From: Michael Roth <mdroth@linux.vnet.ibm.com>
To: Peter Maydell <peter.maydell@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Alexander Graf <agraf@suse.de>,
Anthony Liguori <aliguori@amazon.com>
Subject: Re: [Qemu-devel] QEMU 2.1 release schedule?
Date: Thu, 08 May 2014 20:07:51 -0500 [thread overview]
Message-ID: <20140509010751.4174.76670@loki> (raw)
In-Reply-To: <CAFEAcA-35DTFSZKdtfYZ8pR8_JTm-NT+qnfKYekgB=uY77zf=w@mail.gmail.com>
Quoting Peter Maydell (2014-05-08 08:48:01)
> On 28 April 2014 16:38, Peter Maydell <peter.maydell@linaro.org> wrote:
> > Thanks to everybody who helped with getting QEMU 2.0 released.
> > The traditional reward for a job well done is another job, which
> > means we should probably work out what the release schedule for
> > 2.1 is going to be.
> >
> > We started 2.1's development phase on 17th April, which means that
> > for a standard 3 month release we're looking at mid to late July
> > release. (Of course if we stick to 3 month releases then the
> > slippage on 2.0 means we'll only have 3 releases this year, not
> > 4; do we care?)
> >
> > I felt we were a bit too aggressive in the schedule this
> > time around, and didn't really leave enough hard-freeze time
> > for producing, testing and stabilizing the release candidates.
> > I think we should probably aim for something more like what
> > 2.0 actually ended up with, rather than our proposed dates
> > (see http://wiki.qemu.org/Planning/2.0).
>
> Paolo suggested on IRC:
>
> > soft freeze mid june, hard freeze beginning of july,
> > release end of july or beginning of august?
>
> Which works for me. Some concrete dates:
> * 17 June: softfreeze and rc0
> [ 2 week softfreeze period ]
> * 1 July: hardfreeze
> [ 4 week hardfreeze period, aiming for
> rc1, rc2, rc3 at about weekly intervals ]
> * 29 July: release
>
> Michael: does that schedule work for you, given you'd
> be doing the tarball-rolling parts?
Looks good, don't see any issues with the proposed schedule on my end.
>
> thanks
> -- PMM
next prev parent reply other threads:[~2014-05-09 1:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAFEAcA9qYPsT5WpgZF0GVvYjvtcxvk_xPSCdY4Z+JNaUWCtb2Q@mail.gmail.com>
2014-05-08 13:48 ` [Qemu-devel] QEMU 2.1 release schedule? Peter Maydell
2014-05-09 1:07 ` Michael Roth [this message]
2014-05-09 11:50 ` 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=20140509010751.4174.76670@loki \
--to=mdroth@linux.vnet.ibm.com \
--cc=agraf@suse.de \
--cc=aliguori@amazon.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 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.