From: Stefan Hajnoczi <stefanha@gmail.com>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: [Qemu-devel] QEMU 2.8 release schedule
Date: Wed, 28 Sep 2016 19:06:11 +0100 [thread overview]
Message-ID: <20160928180610.GA17246@stefanha-x1.localdomain> (raw)
[-- Attachment #1: Type: text/plain, Size: 1226 bytes --]
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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next reply other threads:[~2016-09-28 18:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-28 18:06 Stefan Hajnoczi [this message]
2016-09-29 7:04 ` [Qemu-devel] QEMU 2.8 release schedule Gerd Hoffmann
2016-09-29 7:25 ` Fam Zheng
2016-09-29 7:51 ` Paolo Bonzini
2016-09-29 8:27 ` Gerd Hoffmann
2016-09-29 12:58 ` Stefan Hajnoczi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160928180610.GA17246@stefanha-x1.localdomain \
--to=stefanha@gmail.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).