qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [ANNOUNCE] QEMU 1.1-rc3 release
Date: Wed, 23 May 2012 10:32:40 +0200	[thread overview]
Message-ID: <4FBCA0A8.7000304@redhat.com> (raw)
In-Reply-To: <4FBBA384.4010803@us.ibm.com>

Am 22.05.2012 16:32, schrieb Anthony Liguori:
> Hi,
> 
> On behalf of the QEMU Team, I'd like to announce the availability of the third 
> release candidate for the QEMU 1.1 release.  This release is meant for testing 
> purposes and should not be used in a production environment.
> 
> http://wiki.qemu.org/download/qemu-1.1.0-rc3.tar.bz2
> 
> You can help improve the quality of the QEMU 1.1 release by testing this release 
> and reporting bugs on Launchpad:
> 
> https://bugs.launchpad.net/qemu/
> 
> The release plan for the 1.1 release is available at:
> 
> http://wiki.qemu.org/Planning/1.1
> 
> And a detailed change log is available at:
> 
> http://wiki.qemu.org/ChangeLog/Next
> 
> Known Issues:
> 
>   - There are no known release blockers in -rc3.

I think http://patchwork.ozlabs.org/patch/159570/ or a patch based on
Paolo's description should be considered for the release.

Kevin

  parent reply	other threads:[~2012-05-23  8:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-22 14:32 [Qemu-devel] [ANNOUNCE] QEMU 1.1-rc3 release Anthony Liguori
2012-05-22 15:09 ` Jan Kiszka
2012-05-22 15:33   ` Gerd Hoffmann
2012-05-22 15:13 ` Avi Kivity
2012-05-22 15:54   ` Paolo Bonzini
2012-05-23  8:17 ` Stefan Hajnoczi
2012-05-23  8:22   ` Zhi Yong Wu
2012-05-23  8:32 ` Kevin Wolf [this message]
2012-05-23  8:43 ` Michael Tokarev
2012-05-23 11:55 ` Stefano Stabellini

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=4FBCA0A8.7000304@redhat.com \
    --to=kwolf@redhat.com \
    --cc=aliguori@us.ibm.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).