qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>,
	Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
	Michael Roth <mdroth@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] proposed schedule for 2.11 release
Date: Tue, 10 Oct 2017 18:26:45 +0200	[thread overview]
Message-ID: <7c9386e1-b257-29bd-a344-d36574850b70@redhat.com> (raw)
In-Reply-To: <20171010161008.GM30015@redhat.com>

On 10/10/2017 18:10, Daniel P. Berrange wrote:
> On Tue, Oct 10, 2017 at 03:07:26PM +0100, Peter Maydell wrote:
>> OK, here's a strawman proposal for the 2.11 release cycle,
>> based on aiming for a 5 Dec release date and working backwards
>> with the same cadence as 2.10.
>>
>> 2017-10-31 Soft freeze -- all feature changes must already be in a
>>            pull request that's been sent to the mailing list
>> 2017-11-07 Hard freeze, tag rc0
>> 2017-11-14 Tag rc1
>> 2017-11-21 Tag rc2
>> 2017-11-28 Tag rc3
>> 2017-12-05 Release (or rc4 if we need it)
>> 2017-12-12 Release if we needed an rc4
>>
>> That makes softfreeze in 3 weeks time. I'd rather not push
>> the times back any further because we end up in serious
>> risk of running into the christmas holiday period.
> 
> Soft freeze date is not great from a KVM Forum timing POV - the 31st is
> likely to be a travel day for most of the Red Hat devs.

Might as well have soft freeze on Oct 24 (and keep hard freeze on Nov
7)...  Non-maintainers posting patches on the Oct 24-31 week probably
wouldn't have them included in 2.11 anyway.

Paolo

> That said I don't see a much nicer alternative, since giving two weeks
> grace before xmas is good, to allow time for slippage in worst case
> scenarios.
> 
> I guess, it in effect just means that most soft freeze work will want to
> be front loaded in the next 2 weeks before KVM Forum travel starts impacting
> working time.
> 
> Regards,
> Daniel
> 

  reply	other threads:[~2017-10-10 16:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-10 14:07 [Qemu-devel] proposed schedule for 2.11 release Peter Maydell
2017-10-10 16:10 ` Daniel P. Berrange
2017-10-10 16:26   ` Paolo Bonzini [this message]
2017-10-12 18:54     ` 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=7c9386e1-b257-29bd-a344-d36574850b70@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=berrange@redhat.com \
    --cc=mdroth@linux.vnet.ibm.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).