qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org, Peter Maydell <peter.maydell@linaro.org>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] QEMU 2.8 release schedule
Date: Thu, 29 Sep 2016 13:58:37 +0100	[thread overview]
Message-ID: <20160929125837.GC5916@stefanha-x1.localdomain> (raw)
In-Reply-To: <1475132640.25046.13.camel@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 859 bytes --]

On Thu, Sep 29, 2016 at 09:04:00AM +0200, 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.

Good point.  I've updated the wiki with a warning to avoid confusion for
this release.  After this release we can rename it.
http://qemu-project.org/Planning/SoftFeatureFreeze

Stefan

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]

      parent reply	other threads:[~2016-09-29 12:58 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
2016-09-29 12:58   ` Stefan Hajnoczi [this message]

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=20160929125837.GC5916@stefanha-x1.localdomain \
    --to=stefanha@gmail.com \
    --cc=kraxel@redhat.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 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).