From: Michael Roth <mdroth@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org
Subject: [Qemu-devel] [ANNOUNCE] QEMU 2.6.0-rc2 is now available
Date: Thu, 14 Apr 2016 17:21:38 -0500 [thread overview]
Message-ID: <20160414222138.4247.86389@loki> (raw)
Hello,
On behalf of the QEMU Team, I'd like to announce the availability of the
third release candidate for the QEMU 2.6 release. This release is meant
for testing purposes and should not be used in a production environment.
http://wiki.qemu.org/download/qemu-2.6.0-rc2.tar.bz2
A note from the maintainer regarding this RC:
There are still a few bugs outstanding that are probably release
critical, but I'd like to encourage people to (a) get any remaining
critical bug fixes in before rc3 next week and (b) not to put in too
much stuff that's not a critical bug fix. This should maximise our
chances of having rc3 be our last RC before final release on schedule
on the 26th...
You can help improve the quality of the QEMU 2.6 release by testing this
release and reporting bugs on Launchpad:
https://bugs.launchpad.net/qemu/
The release plan, as well a documented known issues for release
candidates, are available at:
http://wiki.qemu.org/Planning/2.6
Please add entries to the ChangeLog for the 2.6 release below:
http://wiki.qemu.org/ChangeLog/2.6
reply other threads:[~2016-04-14 22:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20160414222138.4247.86389@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 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).