On Wed, Nov 23, 2022 at 11:11:03AM +0100, Gerd Hoffmann wrote:
On Tue, Nov 22, 2022 at 01:32:20PM -0500, Kevin O'Connor wrote:
FWIW, if we want a release in the short term, I'd suggest making a v1.16.1 "stable" release.
Well. Currently we have ...
# git log --oneline rel-1.16.0.. 3208b098f51a virtio: finalize features before using device 5ea5c64c20e9 virtio-mmio: read/write the hi 32 features for mmio 61e901bbaadf acpi: parse Alias object 85d56f812f4d virtio-blk: Fix incorrect type conversion in virtio_blk_op() 46de2eec93bf virtio-blk: use larger default request size dc88f9b72df5 malloc: use large ZoneHigh when there is enough memory 3b91e8e9fe93 malloc: use variable for ZoneHigh size 01774004c7f7 reset: force standard PCI configuration access d24f42b0d819 pci: refactor the pci_config_*() functions... where most changes (all except the two 'malloc' patches) are bugfixes. Cherry-picking 7/9 patches into 1.16.1 feels somewhat silly. Just grabbing a master branch snapshot looks like the simpler solution here.
Well, FWIW, I don't see an issue with tagging the master branch as v1.16.1 .
Independent from that I think it makes sense to plan a new 1.17.0 release.
I'm also fine with making a v1.17.0 release. I'd prefer to schedule that though and I'm not sure the timeframe would meet the qemu release goals.
Cheers, -Kevin