From: Peter Maydell <peter.maydell@linaro.org>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Blue Swirl <blauwirbel@gmail.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [RFC] QEMU 1.2.0 Release Schedule
Date: Sat, 2 Jun 2012 23:11:17 +0100 [thread overview]
Message-ID: <CAFEAcA-pyB7Uyv5zn-UnC1AgLTojPBbfsAHZd-oav5V5SkcvjQ@mail.gmail.com> (raw)
In-Reply-To: <4FCA8E86.4000808@codemonkey.ws>
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? One option would be
to decouple these two things by actually branching for release
at some point so we can reopen master before release.
-- PMM
next prev parent reply other threads:[~2012-06-02 22:11 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 [this message]
2012-06-02 22:26 ` Anthony Liguori
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=CAFEAcA-pyB7Uyv5zn-UnC1AgLTojPBbfsAHZd-oav5V5SkcvjQ@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=anthony@codemonkey.ws \
--cc=blauwirbel@gmail.com \
--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).