From: Stefan Hajnoczi <stefanha@gmail.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Stefan Hajnoczi <stefanha@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Proposal for 2.9 release schedule
Date: Tue, 3 Jan 2017 15:53:47 +0000 [thread overview]
Message-ID: <20170103155347.GF14707@stefanha-x1.localdomain> (raw)
In-Reply-To: <a6803686-9435-0276-0118-10961dc97e04@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 953 bytes --]
On Fri, Dec 23, 2016 at 03:15:58PM +0100, Paolo Bonzini wrote:
> Considering that Easter is on April 16th, we'd probably want to have the
> release before that date even in case of a slip.
>
> On the other hand, the Christmas / New Year break here means that we'll
> have to make the development time 1-2 week shorter in practice.
>
> 2016-02-21 2.9 soft freeze
> 2016-03-07 hard freeze / rc0
> 2016-03-28 rc3 (+3 weeks)
> 2016-04-04 rc4 or release
> 2016-04-11 release (if rc4)
>
> One possibility is to make soft freeze happen a few days later.
> Peter/Stefan, how did the experiment go with the new rules for soft
> freeze? Is it worth repeating it for 2.9 and would it make sense to
> shorten soft freeze given the new rules?
I would shorten the soft freeze by 1 week.
Overall the 2.8 release went smoothly. We got unlucky right at the end
with a release blocker but otherwise it was fine.
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2017-01-03 15:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-23 14:15 [Qemu-devel] Proposal for 2.9 release schedule Paolo Bonzini
2017-01-03 15:53 ` Stefan Hajnoczi [this message]
2017-01-03 16:06 ` Paolo Bonzini
2017-01-04 14:51 ` Stefan Hajnoczi
2017-01-06 15:12 ` Peter Maydell
2017-01-09 10:41 ` Stefan Hajnoczi
2017-01-09 11:11 ` Peter Maydell
2017-01-09 12:27 ` Paolo Bonzini
2017-03-13 18:13 ` Peter Maydell
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=20170103155347.GF14707@stefanha-x1.localdomain \
--to=stefanha@gmail.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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).