Let's use the following release schedule, originally proposed by Paolo Bonzini, for QEMU 2.8:
2016-11-01 softfreeze 2016-11-15 hardfreeze/rc0 (+2 weeks) 2016-11-22 rc1 (+1 week) 2016-11-29 rc2 (+1 week) 2016-12-06 rc3 (+1 week) 2016-12-13 rc4 or release (+1 week) 2016-12-20 release if rc4 was necessary Wiki page: http://qemu-project.org/Planning/2.8 Changelog: http://qemu-project.org/ChangeLog/2.8 Following previous discussions [1], the rules for the softfreeze will be changed in the QEMU 2.8 release cycle to bound the length of the freeze period better. Previously patch series posted on the mailing list prior to softfreeze could be included in maintainers' pull requests during softfreeze. Going forward pull requests sent by maintainers during softfreeze must contain only bug fixes. Of course v2 pull requests are allowed if there was a build/test failure with the final non-softfreeze pull request. The result is that the 2 week softfreeze period will allow rc0 to be tagged reliably under less code churn. I have posted this schedule on the wiki and updated the softfreeze wiki page. Please reply if you have any concerns. Stefan [1] https://lists.gnu.org/archive/html/qemu-devel/2016-09/msg00057.html
signature.asc
Description: PGP signature
