From: Gerd Hoffmann <kraxel@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Fam Zheng <famz@redhat.com>, Stefan Hajnoczi <stefanha@gmail.com>,
Peter Maydell <peter.maydell@linaro.org>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] QEMU 2.8 release schedule
Date: Thu, 29 Sep 2016 10:27:15 +0200 [thread overview]
Message-ID: <1475137635.25046.29.camel@redhat.com> (raw)
In-Reply-To: <41d2fb70-62fa-158c-80ac-ea7f7ba80bc8@redhat.com>
On Do, 2016-09-29 at 09:51 +0200, Paolo Bonzini wrote:
>
> On 29/09/2016 09:25, Fam Zheng wrote:
> > On Thu, 09/29 09:04, Gerd Hoffmann wrote:
> >> Hi,
> >>
> >>> Following previous discussions [1], the rules for the softfreeze will be
> >>> changed in the QEMU 2.8 release cycle to bound the length of the freeze
> >>> period better.
> >>>
> >>> Previously patch series posted on the mailing list prior to softfreeze
> >>> could be included in maintainers' pull requests during softfreeze.
> >>
> >> Maybe we should call "softfreeze" simple "freeze" then to make things
> >> more clear. Any features must land pull requests before freeze, period.
> >> We don't really have a separate hard freeze any more: After (soft-)
> >> freeze only bugfixes are allowed.
> >
> > +1. The new rule for softfreeze is already changing it to a "hard" one.
>
> For maintainers there is a difference in that you have some more time to
> resend failed pull requests.
Yes, before -rc0 it's allowed to have bugfixes for pending pull
requests, after -rc0 it's only bugfixes for merged code.
But in any case feature pull requests must be on the list before (soft)
freeze, which is what matters most for everybody's planning.
cheers,
Gerd
next prev parent reply other threads:[~2016-09-29 8:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-28 18:06 [Qemu-devel] QEMU 2.8 release schedule Stefan Hajnoczi
2016-09-29 7:04 ` Gerd Hoffmann
2016-09-29 7:25 ` Fam Zheng
2016-09-29 7:51 ` Paolo Bonzini
2016-09-29 8:27 ` Gerd Hoffmann [this message]
2016-09-29 12:58 ` Stefan Hajnoczi
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=1475137635.25046.29.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=famz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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 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).