From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:54009)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <kraxel@redhat.com>) id 1bpWgb-00067L-Uz
	for qemu-devel@nongnu.org; Thu, 29 Sep 2016 04:27:22 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <kraxel@redhat.com>) id 1bpWgY-0005pC-OS
	for qemu-devel@nongnu.org; Thu, 29 Sep 2016 04:27:21 -0400
Received: from mx1.redhat.com ([209.132.183.28]:40488)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <kraxel@redhat.com>) id 1bpWgY-0005p0-Hs
	for qemu-devel@nongnu.org; Thu, 29 Sep 2016 04:27:18 -0400
Message-ID: <1475137635.25046.29.camel@redhat.com>
From: Gerd Hoffmann <kraxel@redhat.com>
Date: Thu, 29 Sep 2016 10:27:15 +0200
In-Reply-To: <41d2fb70-62fa-158c-80ac-ea7f7ba80bc8@redhat.com>
References: <20160928180610.GA17246@stefanha-x1.localdomain>
	<1475132640.25046.13.camel@redhat.com> <20160929072509.GA2432@lemon>
	<41d2fb70-62fa-158c-80ac-ea7f7ba80bc8@redhat.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0
Subject: Re: [Qemu-devel] QEMU 2.8 release schedule
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel/>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
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

On Do, 2016-09-29 at 09:51 +0200, Paolo Bonzini wrote:
>=20
> 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 free=
ze
> >>> period better.
> >>>
> >>> Previously patch series posted on the mailing list prior to softfreez=
e
> >>> 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, perio=
d.
> >> We don't really have a separate hard freeze any more:  After (soft-)
> >> freeze only bugfixes are allowed.
> >=20
> > +1. The new rule for softfreeze is already changing it to a "hard" one.
>=20
> 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