All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Blue Swirl <blauwirbel@gmail.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [RFC] QEMU 1.2.0 Release Schedule
Date: Sun, 03 Jun 2012 06:26:15 +0800	[thread overview]
Message-ID: <4FCA9307.2090508@codemonkey.ws> (raw)
In-Reply-To: <CAFEAcA-pyB7Uyv5zn-UnC1AgLTojPBbfsAHZd-oav5V5SkcvjQ@mail.gmail.com>

On 06/03/2012 06:11 AM, Peter Maydell wrote:
> On 2 June 2012 23:07, Anthony Liguori<anthony@codemonkey.ws>  wrote:
>> On 06/03/2012 04:16 AM, Blue Swirl wrote:
>>> I think the previous freeze was a bit long, mainly the problem is how
>>> to handle merging of different development trees (QOM vs. PPC for
>>> example). So 2,5 weeks could be nice.
>>
>> Yes, I feel it was a little long also.
>
> I agree that the period when master was closed was too long,
> but if we shorten the freeze period will we still have time
> to collect all the bugfixes that crop up?

I felt it was a bit too long because unlike the 1.0 release and previous 0.15 
release, we didn't have any major issues that needed fixing during -rc.  I 
attribute that to the fact that we did a little bit more planning up front and 
avoided surprises.

> One option would be
> to decouple these two things by actually branching for release
> at some point so we can reopen master before release.

I really don't want to do that.  That's the method we used for the early part of 
our history.  It resulted in a lot of people ignoring the releases entirely. 
Freezing master causes everyone to focus on the release instead of future 
looking development.  That's a feature, not a bug :-)

Regards,

Anthony Liguori

>
> -- PMM
>

      reply	other threads:[~2012-06-02 22:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-02  9:52 [Qemu-devel] [RFC] QEMU 1.2.0 Release Schedule Anthony Liguori
2012-06-02 20:16 ` Blue Swirl
2012-06-02 22:07   ` Anthony Liguori
2012-06-02 22:11     ` Peter Maydell
2012-06-02 22:26       ` Anthony Liguori [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=4FCA9307.2090508@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=blauwirbel@gmail.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 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.