Planning/5.2: Difference between revisions

From QEMU
Line 60: Line 60:
*  qcow2: Regression that potentially causes corruption on write_zeroes with MAY_UNMAP
*  qcow2: Regression that potentially causes corruption on write_zeroes with MAY_UNMAP
** fix: https://lists.gnu.org/archive/html/qemu-block/2020-11/msg00674.html
** fix: https://lists.gnu.org/archive/html/qemu-block/2020-11/msg00674.html
 
* set_pci_host_devaddr() fails parsing bus > 0x1f
** fix: https://www.mail-archive.com/qemu-devel@nongnu.org/msg761406.html


=== Will not be fixed in 5.2 ===
=== Will not be fixed in 5.2 ===
Line 71: Line 72:
=== Not fixed yet ===
=== Not fixed yet ===


* set_pci_host_devaddr() fails parsing bus > 0x1f
** fix: https://www.mail-archive.com/qemu-devel@nongnu.org/msg761406.html
* pci broken for s390x-on-x86 tcg guests, bisected to 28dc86a07299 ("s390x/pci: use a PCI Group structure") (https://lore.kernel.org/qemu-devel/20201117124349.2e1e2fe3.cohuck@redhat.com/)
* pci broken for s390x-on-x86 tcg guests, bisected to 28dc86a07299 ("s390x/pci: use a PCI Group structure") (https://lore.kernel.org/qemu-devel/20201117124349.2e1e2fe3.cohuck@redhat.com/)
** fix: https://lore.kernel.org/qemu-devel/20201118104202.1301363-1-cohuck@redhat.com/
** fix: https://lore.kernel.org/qemu-devel/20201118104202.1301363-1-cohuck@redhat.com/

Revision as of 21:11, 24 November 2020

Release Schedule

2020-08-12 Beginning of development phase
2020-10-27 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.
2020-11-03 Hard feature freeze. Tag rc0
2020-11-10 Tag rc1
2020-11-17 Tag rc2
2020-11-24 Tag rc3
2020-12-01 Release; or tag rc4 if needed
2020-12-08 Release if we needed an 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 rc1

Fixed in rc2

Fixed in rc3

Will not be fixed in 5.2

Not fixed yet

Targeted Features

See the ChangeLog/5.2 for full details.