From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1Mt0RX-0003eI-5U
	for qemu-devel@nongnu.org; Wed, 30 Sep 2009 10:46:11 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1Mt0RS-0003cX-Nn
	for qemu-devel@nongnu.org; Wed, 30 Sep 2009 10:46:10 -0400
Received: from [199.232.76.173] (port=44868 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Mt0RS-0003cP-DQ
	for qemu-devel@nongnu.org; Wed, 30 Sep 2009 10:46:06 -0400
Received: from e31.co.us.ibm.com ([32.97.110.149]:49158)
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60)
	(envelope-from <aliguori@us.ibm.com>) id 1Mt0RR-0006dy-Aj
	for qemu-devel@nongnu.org; Wed, 30 Sep 2009 10:46:05 -0400
Received: from d03relay05.boulder.ibm.com (d03relay05.boulder.ibm.com
	[9.17.195.107])
	by e31.co.us.ibm.com (8.14.3/8.13.1) with ESMTP id n8UEdi92001408
	for <qemu-devel@nongnu.org>; Wed, 30 Sep 2009 08:39:44 -0600
Received: from d03av03.boulder.ibm.com (d03av03.boulder.ibm.com [9.17.195.169])
	by d03relay05.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id
	n8UEjhYM038768
	for <qemu-devel@nongnu.org>; Wed, 30 Sep 2009 08:45:44 -0600
Received: from d03av03.boulder.ibm.com (loopback [127.0.0.1])
	by d03av03.boulder.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id
	n8UEjXrD001653
	for <qemu-devel@nongnu.org>; Wed, 30 Sep 2009 08:45:34 -0600
Message-ID: <4AC36F0C.8020400@us.ibm.com>
Date: Wed, 30 Sep 2009 09:45:32 -0500
From: Anthony Liguori <aliguori@us.ibm.com>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] Release plan for 0.12.0
References: <4AC29E4D.80707@us.ibm.com> <20090930103001.21aa7a8d@doriath>
In-Reply-To: <20090930103001.21aa7a8d@doriath>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: kvm-devel <kvm@vger.kernel.org>, "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>, Blue Swirl <blauwirbel@gmail.com>, Paul Brook <paul@codesourcery.com>, "Edgar E. Iglesias" <edgar.iglesias@gmail.com>, Aurelien Jarno <aurelien@aurel32.net>

Luiz Capitulino wrote:
> On Tue, 29 Sep 2009 18:54:53 -0500
> Anthony Liguori <aliguori@us.ibm.com> wrote:
>
>   
>> I think aiming for early to mid-December would give us roughly a 3 month 
>> cycle and would align well with some of the Linux distribution cycles.  
>> I'd like to limit things to a single -rc that lasted only for about a 
>> week.  This is enough time to fix most of the obvious issues I think.
>>     
>
>  How do you plan to do it? I mean, are you going to create a separate branch
> or make master the -rc?
>
>  Creating a separate branch (which is what we do today, iiuc) makes it
> get less attention, freezing master for a certain period is the best
> way to stabilize.
>
>  Is this what you had in mind?
>   
What do people think?

One reason I branch is because some people care a bit less about 
releases so it makes the process non-disruptive to them.  If the other 
maintainers agreed though, I would certainly like to have the master 
branch essentially frozen for the week before the release.

-- 
Regards,

Anthony Liguori