Planning/3.0: Difference between revisions
(valgrind issue with mps2-an505) |
|||
Line 40: | Line 40: | ||
* Valgrind complains about uninitialized value here: <code>valgrind -q aarch64-softmmu/qemu-system-aarch64 -M mps2-an505,accel=qtest</code> | * Valgrind complains about uninitialized value here: <code>valgrind -q aarch64-softmmu/qemu-system-aarch64 -M mps2-an505,accel=qtest</code> | ||
* migration crash with -device hda-duplex | |||
=== Issues that will not be fixed === | === Issues that will not be fixed === |
Revision as of 10:25, 24 July 2018
Release Schedule
2018-04-24 | Beginning of development phase |
2018-07-03 | Soft feature freeze. Only bug fixes after this point. All feature changes must be already in a sub maintainer tree and all pull requests from submaintainers must have been sent to the list by this date. |
2018-07-10 | Hard feature freeze. Tag rc0 |
2018-07-17 | Tag rc1 |
2018-07-24 | Tag rc2 |
2018-07-31 | Tag rc3 |
2018-08-07 | Release, or if necessary, tag rc4 |
2018-08-14 | Release, if we needed rc4 |
Known issues
Please list all patch series or bugs which need to be fixed for the release here. That way I can be sure I don't miss any when I'm rolling release candidates.
Fixed in rc0
Fixed in rc1
- Crash with:
qemu-system-aarch64 -M integratorcp,accel=qtest -nographic
and then at the HMP monitor:device_add bcm2837
followed bydevice_add corgi-ssp
Not yet fixed in any rc
- Valgrind complains about uninitialized value here:
valgrind -q aarch64-softmmu/qemu-system-aarch64 -M mps2-an505,accel=qtest
- migration crash with -device hda-duplex
Issues that will not be fixed
Targeted Features
See the ChangeLog/3.0 for full details.