|
From: | Anthony Liguori |
Subject: | Re: [Qemu-devel] [RFC] QEMU 1.2.0 Release Schedule |
Date: | Sun, 03 Jun 2012 06:26:15 +0800 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20120329 Thunderbird/11.0.1 |
On 06/03/2012 06:11 AM, Peter Maydell wrote:
On 2 June 2012 23:07, Anthony Liguori<address@hidden> 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
[Prev in Thread] | Current Thread | [Next in Thread] |