From mboxrd@z Thu Jan 1 00:00:00 1970 From: Luiz Capitulino Subject: Re: [Qemu-devel] Release plan for 0.12.0 Date: Wed, 30 Sep 2009 10:30:01 -0300 Message-ID: <20090930103001.21aa7a8d@doriath> References: <4AC29E4D.80707@us.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: "qemu-devel@nongnu.org" , Paul Brook , kvm-devel To: Anthony Liguori Return-path: Received: from mx1.redhat.com ([209.132.183.28]:12814 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752730AbZI3Na1 (ORCPT ); Wed, 30 Sep 2009 09:30:27 -0400 In-Reply-To: <4AC29E4D.80707@us.ibm.com> Sender: kvm-owner@vger.kernel.org List-ID: On Tue, 29 Sep 2009 18:54:53 -0500 Anthony Liguori 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?