qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
	Stefan Hajnoczi <stefanha@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>, Stefan Hajnoczi <stefanha@gmail.com>
Subject: Re: [Qemu-devel] Proposal for 2.9 release schedule
Date: Mon, 9 Jan 2017 13:27:13 +0100	[thread overview]
Message-ID: <7bcc9ad8-6538-beeb-e1d4-f84f4d5a5eab@redhat.com> (raw)
In-Reply-To: <CAFEAcA8xO1JER27=7sR3CQBTeUs=VkuLjT+ypGMgA9te_5Q4tg@mail.gmail.com>



On 09/01/2017 12:11, Peter Maydell wrote:
> On 9 January 2017 at 10:41, Stefan Hajnoczi <stefanha@redhat.com> wrote:
>> On Fri, Jan 06, 2017 at 03:12:28PM +0000, Peter Maydell wrote:
>>> On 4 January 2017 at 14:51, Stefan Hajnoczi <stefanha@redhat.com> wrote:
>>>> On Tue, Jan 03, 2017 at 05:06:13PM +0100, Paolo Bonzini wrote:
>>>>> On 03/01/2017 16:53, Stefan Hajnoczi wrote:
>>>>>> 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.
>>>>>
>>>>> Then what about soft freeze on 2016-02-28?
>>>>
>>>> Sounds good to me.  Peter?
>>>
>>> Are we retaining the "make sure you have your pull requests on the list
>>> by the softfreeze date" rule this time around?
>>
>> I hope so.  It helps keep the freeze time bounded.
> 
> OK. The dates above work ok for me, so I've updated the wiki:
> http://wiki.qemu.org/Planning/2.9
> 
> If we're going to standardize on the new softfreeze definition we should
> update http://wiki.qemu.org/Planning/SoftFeatureFreeze I guess.

Done, any help with the wording is welcome of course.

Paolo

  reply	other threads:[~2017-01-09 12:27 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
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 [this message]
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=7bcc9ad8-6538-beeb-e1d4-f84f4d5a5eab@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    --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).