All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Stefan Hajnoczi <stefanha@redhat.com>,
	Peter Maydell <peter.maydell@linaro.org>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] proposed release timetable for 2.8
Date: Tue, 6 Sep 2016 09:52:06 +0200	[thread overview]
Message-ID: <10cce380-1a5e-e507-23ff-b09ae70b4acd@redhat.com> (raw)
In-Reply-To: <20160906024335.cfmygl6rj4gssolg@redhat.com>



On 06/09/2016 04:43, Michael S. Tsirkin wrote:
> > Based also on the discussion at QEMU summit, where there was consensus
> > that three weeks between softfreeze and rc0 was too much, IMO we can
> > shorten the period to just two weeks
> 
> Do we intend to strengthen the soft freeze definition then?
> One difficulty is that the definition for soft freeze at the moment is
> that some code is on list.  Some of these get reworked significantly.

Yes, see Peter's answer to me.

> I get flooded with patches just before the softfreeze, all conflicting,
> all need some work, and it takes a bunch of back and forth to resolve
> the conflicts.

You are too good! :)

Paolo

  reply	other threads:[~2016-09-06  7:52 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 [this message]
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
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=10cce380-1a5e-e507-23ff-b09ae70b4acd@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=mst@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.