From: Michael Roth <mdroth@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org
Subject: [ANNOUNCE] QEMU 4.2.0-rc4 is now available
Date: Tue, 03 Dec 2019 13:45:20 -0600 [thread overview]
Message-ID: <157540232094.32150.6482163876120353790@sif> (raw)
Hello,
On behalf of the QEMU Team, I'd like to announce the availability of the
fifth release candidate for the QEMU 4.2 release. This release is meant
for testing purposes and should not be used in a production environment.
http://download.qemu-project.org/qemu-4.2.0-rc4.tar.xz
http://download.qemu-project.org/qemu-4.2.0-rc4.tar.xz.sig
A note from the maintainer:
rc4 has a small collection of bugfixes which didn't quite make rc3.
Unless there is a critical bug discovered in the next week, we
plan to release 4.2.0 on Tuesday 10th December.
You can help improve the quality of the QEMU 4.2 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/4.2
Please add entries to the ChangeLog for the 4.2 release below:
http://wiki.qemu.org/ChangeLog/4.2
Thank you to everyone involved!
Changes since rc3:
1bdc319ab5: Update version for v4.2.0-rc4 release (Peter Maydell)
64bef038e7: hvf: correctly inject VMCS_INTR_T_HWINTR versus VMCS_INTR_T_SWINTR. (Cameron Esfahani)
cb09104ea8: block/file-posix: Fix laio_init() error handling crash bug (Markus Armbruster)
5a0948d36c: net/virtio: Fix failover error handling crash bugs (Markus Armbruster)
4dbac1aed2: net/virtio: Drop useless n->primary_dev not null checks (Markus Armbruster)
fb2246882a: .travis.yml: drop xcode9.4 from build matrix (Alex Bennée)
bf876a688c: pc-bios/s390: Update firmware image with the "fix sclp_get_loadparm_ascii" patch (Thomas Huth)
f24ec9fead: pc-bios/s390-ccw: fix sclp_get_loadparm_ascii (Claudio Imbrenda)
reply other threads:[~2019-12-03 21:17 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=157540232094.32150.6482163876120353790@sif \
--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).