Planning/4.0: Difference between revisions

From QEMU
 
(14 intermediate revisions by 4 users not shown)
Line 27: Line 27:
| 2019-04-23
| 2019-04-23
| Release, if we needed an rc4.
| Release, if we needed an rc4.
|-
| 2019-10-10
| Freeze for v4.0.1
|-
| 2019-10-17
| Tag v4.0.1
|}
|}


Line 59: Line 65:
* arithmetic overflow in load_device_tree()
* arithmetic overflow in load_device_tree()


=== Will be fixed in rc4 ===
=== Fixed in rc4 ===


* broken naming of root PCI buses for spapr PHBs https://lists.gnu.org/archive/html/qemu-devel/2019-04/msg019
* broken naming of root PCI buses for spapr PHBs https://lists.gnu.org/archive/html/qemu-devel/2019-04/msg019
* warning compiling curses.c on some 32-bit systems https://patchew.org/QEMU/20190402073018.17747-1-kraxel%40redhat.com/56.html
* warning compiling curses.c on some 32-bit systems https://patchew.org/QEMU/20190402073018.17747-1-kraxel%40redhat.com/56.html
* qemu-img doc consistency https://lists.gnu.org/archive/html/qemu-devel/2019-04/msg01548.html
* qemu-img doc consistency https://lists.gnu.org/archive/html/qemu-devel/2019-04/msg01548.html
* iotest 241 failure https://lists.gnu.org/archive/html/qemu-devel/2019-04/msg01725.html
* iotest 245 failure https://lists.gnu.org/archive/html/qemu-devel/2019-04/msg01682.html
* gcc -O3 buildfix in slirp code
* "[PATCH] socket: allow wait=false for client socket" (regression affects libvirt use of chardev) https://lists.gnu.org/archive/html/qemu-devel/2019-04/msg02548.html
* qcow2: Fix potential corruption for preallocated resize with external data file
* "0/3 usb-mtp: fix ObjectInfo request handling" (potential guest-triggered security issue, read off end of buffer, only present if you're using usb-mtp and have explicitly enabled write support) https://lists.gnu.org/archive/html/qemu-devel/2019-04/msg02524.html -- have applied just patch 2 which is the security fix and looks safe to me


=== Not yet fixed in any rc ===
=== Not yet fixed in any rc ===
* Nice to have:
** fix delvm interaction with libvirt https://lists.gnu.org/archive/html/qemu-devel/2019-04/msg01699.html
** iotest 241 failure https://lists.gnu.org/archive/html/qemu-devel/2019-04/msg01725.html
** iotest 245 failure https://lists.gnu.org/archive/html/qemu-devel/2019-04/msg01682.html


=== Issues that will not be fixed ===
=== Issues that will not be fixed ===


* fix delvm interaction with libvirt https://lists.gnu.org/archive/html/qemu-devel/2019-04/msg01699.html (not a regression)
* allow seccomp to be used on archs other than x86/mips/ppc/arm/s390x (not a regression)
* allow seccomp to be used on archs other than x86/mips/ppc/arm/s390x (not a regression)



Latest revision as of 23:44, 1 October 2019

Release Schedule

Tentatively proposed dates, still to be discussed/agreed.

2018-12-12 Beginning of development phase
2019-03-12 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.
2019-03-19 Hard feature freeze. Tag rc0
2019-03-26 Tag rc1
2019-04-02 Tag rc2
2019-04-09 Tag rc3
2019-04-16 Release, or tag rc4 if extra RC cycle needed
2019-04-23 Release, if we needed an rc4.
2019-10-10 Freeze for v4.0.1
2019-10-17 Tag v4.0.1

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

Fixed in rc2

Fixed in rc3

Fixed in rc4

Not yet fixed in any rc

Issues that will not be fixed

Targeted Features

See the ChangeLog/4.0 for full details.