From: "Daniel P. Berrange" <berrange@redhat.com>
To: 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 17:10:08 +0100 [thread overview]
Message-ID: <20171010161008.GM30015@redhat.com> (raw)
In-Reply-To: <CAFEAcA-zUTfLOBkOeLc4e1Ok0dnKD=hWsdeR47125MhMnwV7UA@mail.gmail.com>
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.
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
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2017-10-10 16:10 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 [this message]
2017-10-10 16:26 ` Paolo Bonzini
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=20171010161008.GM30015@redhat.com \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.