From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel <qemu-devel@nongnu.org>
Cc: "Justin M. Forbes" <jmforbes@linuxtx.org>, Avi Kivity <avi@redhat.com>
Subject: [Qemu-devel] Update to 0.15.0 release schedule
Date: Thu, 04 Aug 2011 16:38:29 -0500 [thread overview]
Message-ID: <4E3B1155.3010402@codemonkey.ws> (raw)
Hi,
It took a little longer than I had hoped to converge on a work around
for the migration issue. -rc2 is out but I don't think 24 hours is
enough time to get proper testing for the final release.
So I'm pushing 0.15.0 to Monday. Please test and provide feedback.
Unless there's a brown paper bag bug, -rc2 will be the 0.15.0 release.
I've updated the release schedule on the wiki:
http://wiki.qemu.org/Planning/0.15#Release_Schedule
Regards,
Anthony Liguori
next reply other threads:[~2011-08-04 21:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-04 21:38 Anthony Liguori [this message]
2011-08-05 11:38 ` [Qemu-devel] Update to 0.15.0 release schedule Kevin Wolf
2011-08-05 12:14 ` Anthony Liguori
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E3B1155.3010402@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=jmforbes@linuxtx.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).