From: Anthony Liguori <aliguori@us.ibm.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [ANNOUNCE] QEMU 1.2.0-rc3 release
Date: Tue, 04 Sep 2012 15:27:08 -0500 [thread overview]
Message-ID: <878vcpjzz7.fsf@codemonkey.ws> (raw)
In-Reply-To: <CAAu8pHt9G3buS7=dTOPna+t1TJzNHQtJ96+ir1F=CM34N4r=7Q@mail.gmail.com>
Blue Swirl <blauwirbel@gmail.com> writes:
> On Tue, Sep 4, 2012 at 12:54 PM, Anthony Liguori <aliguori@us.ibm.com> wrote:
>> Hi,
>>
>> On behalf of the QEMU Team, I'd like to announce the availability of the
>> third and final release candidate for the QEMU 1.2 release. This
>> release is meant for testing purposes and should not be used in a
>> production environment.
>>
>> http://wiki.qemu.org/download/qemu-1.2.0-rc3.tar.bz2
>>
>> You can help improve the quality of the QEMU 1.2 release by testing this
>> release and reporting bugs on Launchpad:
>>
>> https://bugs.launchpad.net/qemu/
>>
>> The release plan for the 1.2 release is available at:
>>
>> http://wiki.qemu.org/Planning/1.2
>
> The plan does not mention rc3 and also claims that release will happen
> tomorrow.
The final release will happen tomorrow. I tagged -rc3 last week but
never announced it.
-rc3 was a compromise because a couple pull requests came in too late
for -rc2.
I didn't update Planning for it but should have.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2012-09-04 20:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-04 12:54 [Qemu-devel] [ANNOUNCE] QEMU 1.2.0-rc3 release Anthony Liguori
2012-09-04 19:29 ` Blue Swirl
2012-09-04 19:42 ` Peter Maydell
2012-09-04 20:06 ` Blue Swirl
2012-09-04 20:28 ` Anthony Liguori
2012-09-04 20:27 ` Anthony Liguori [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-08-23 16:05 anthony
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=878vcpjzz7.fsf@codemonkey.ws \
--to=aliguori@us.ibm.com \
--cc=blauwirbel@gmail.com \
--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).