From: Michael Roth <mdroth@linux.vnet.ibm.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [ANNOUNCE] QEMU 2.0.0-rc1 is now available
Date: Thu, 03 Apr 2014 15:16:39 -0500 [thread overview]
Message-ID: <20140403201639.15125.13982@loki> (raw)
In-Reply-To: <CAFEAcA_pPUezWdhmqGe+YN5tkG9YYikYJZu90--8L7akrnapbg@mail.gmail.com>
Quoting Peter Maydell (2014-04-03 15:02:36)
> On 3 April 2014 20:49, Michael Roth <mdroth@linux.vnet.ibm.com> wrote:
> > Hello,
> >
> > On behalf of the QEMU Team, I'd like to announce the availability of the
> > second release candidate for the QEMU 2.0 release. This release is meant
> > for testing purposes and should not be used in a production environment.
> >
> > http://wiki.qemu.org/download/qemu-2.0.0-rc1.tar.bz2
> >
> > You can help improve the quality of the QEMU 2.0 release by testing this
> > release and reporting bugs on Launchpad:
> >
> > https://bugs.launchpad.net/qemu/
> >
> > The release plan for the 2.0 release is available at:
> >
> > http://wiki.qemu.org/Planning/2.0
>
> We should probably update this -- we slipped a couple of days
> on the rc1, and I know there are still some fixes that will
> require an rc2. How about:
> rc2 7th or 8th April
> release 2 days after (assuming no fixes appear that need to
> go into an rc3)
I think that seems reasonable, couple extra days to test rc1 to make up for
the slippage, then a couple for the additional rc2.
>
> ?
>
> thanks
> -- PMM
next prev parent reply other threads:[~2014-04-03 20:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-03 19:49 [Qemu-devel] [ANNOUNCE] QEMU 2.0.0-rc1 is now available Michael Roth
2014-04-03 20:02 ` Peter Maydell
2014-04-03 20:16 ` Michael Roth [this message]
2014-04-04 14:39 ` Stefan Hajnoczi
2014-04-04 14:57 ` Peter Maydell
2014-04-04 19:10 ` Paolo Bonzini
2014-04-04 19:31 ` Kevin Wolf
2014-04-04 5:17 ` Stefan Weil
2014-04-04 15:37 ` Michael Roth
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=20140403201639.15125.13982@loki \
--to=mdroth@linux.vnet.ibm.com \
--cc=peter.maydell@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.