From: Markus Armbruster <armbru@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Kevin Wolf <kwolf@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] proposed release timetable for 2.8
Date: Tue, 06 Sep 2016 14:40:21 +0200 [thread overview]
Message-ID: <87pooh2ocq.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <CAFEAcA_NRpiPon4PoGN0qEcyuzsqg+8ayt9k6aJ07fCDO9FtmA@mail.gmail.com> (Peter Maydell's message of "Tue, 6 Sep 2016 11:40:54 +0100")
Peter Maydell <peter.maydell@linaro.org> writes:
> On 6 September 2016 at 11:33, Kevin Wolf <kwolf@redhat.com> wrote:
>> Am 05.09.2016 um 13:10 hat Peter Maydell geschrieben:
>>> 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?
>>
>> I don't think we should leave a bug intentionally unfixed even though
>> there is a patch, just because it was already broken in the last
>> release.
>
> We already do (informally) once we're a way into the hard freeze.
> Bug reports (and fixes for them) arrive all the time, and at
> a rate such that if we allowed any bug fix into the
> tree during freeze we would never have a period of a week
> without new bugfixes going in that allowed us to actually
> release.
>
> If a bug went unnoticed and unfixed for almost the whole release
> cycle, this is a good sign that it's actually not all that
> prominent to users; so it's a reasonably good, objective,
> and easy to apply metric for restricting bug fixes to "only
> important bug fixes".
In short, we use common sense to throttle the flow of bug fixes, so we
can get a release out of the door.
next prev parent reply other threads:[~2016-09-06 12:40 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
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 [this message]
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=87pooh2ocq.fsf@dusky.pond.sub.org \
--to=armbru@redhat.com \
--cc=kwolf@redhat.com \
--cc=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.