All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: QEMU Developers <qemu-devel@nongnu.org>
Cc: Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] proposed release timetable for 2.8
Date: Mon, 5 Sep 2016 12:10:35 +0100	[thread overview]
Message-ID: <CAFEAcA97PvZbqGoF2AqZzfEb7L2Yadi9retmPyxT7JWK2VFYww@mail.gmail.com> (raw)
In-Reply-To: <CAFEAcA9J6Yxqqeg+BzEjNJfuX1Zr93i3797J+3QD-HXHMANUew@mail.gmail.com>

On 1 September 2016 at 12:18, Peter Maydell <peter.maydell@linaro.org> wrote:
> I know 2.7 isn't quite out the door yet, but I figured we should
> kick off the discussion of 2.8's schedule. At the QEMU Summit there
> was some discussion on how we're doing with releases, and I think
> the consensus view was that we should try to cut down the softfreeze
> period and also be stricter about (a) making sure pull requests get
> in in a timely way before rc0 and (b) we don't take new features
> during softfreeze.

It occurs to me that if anybody has the patience to do some tedious
data-mining, it would be interesting to know for all the commits
that went in after rc0 whether they were:
 * fixing bugs that were already present in our previous release
 * fixing regressions (ie bugs introduced after the previous release)
 * fixing bugs in features that are new in this release
 * new features
 * fixing bugs introduced by other post-rc0 commits
 * security fixes

ie if we were stricter about "no commits unless they're fixes for
regressions, fixes for things new in this release or security fixes",
would this reduce the number of commits we do post-freeze much?

thanks
-- PMM

  parent reply	other threads:[~2016-09-05 11:11 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-01 11:18 [Qemu-devel] proposed release timetable for 2.8 Peter Maydell
2016-09-01 14:08 ` Stefan Hajnoczi
2016-09-05  9:38   ` Kevin Wolf
2016-09-05 18:20     ` Stefan Hajnoczi
2016-09-05 14:47   ` Paolo Bonzini
2016-09-05 15:11     ` Peter Maydell
2016-09-05 15:15       ` Paolo Bonzini
2016-09-14 14:27       ` Stefan Hajnoczi
2016-09-06  2:43     ` Michael S. Tsirkin
2016-09-06  7:52       ` Paolo Bonzini
2016-09-05 11:10 ` Peter Maydell [this message]
2016-09-05 12:09   ` Markus Armbruster
2016-09-06 10:33   ` Kevin Wolf
2016-09-06 10:40     ` Peter Maydell
2016-09-06 12:40       ` Markus Armbruster
2016-09-06 12:43         ` Peter Maydell
2016-09-05 12:34 ` Daniel P. Berrange

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=CAFEAcA97PvZbqGoF2AqZzfEb7L2Yadi9retmPyxT7JWK2VFYww@mail.gmail.com \
    --to=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 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.