From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [Qemu-devel] ANNOUNCE: QEMU 0.10.0 stable branch Date: Sun, 08 Mar 2009 17:31:52 +0200 Message-ID: <49B3E4E8.9080700@redhat.com> References: <49B01FFD.7040900@codemonkey.ws> <49B3A7C1.2090707@redhat.com> <49B3E29F.1080400@codemonkey.ws> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm-devel To: qemu-devel@nongnu.org Return-path: Received: from mx2.redhat.com ([66.187.237.31]:59664 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752282AbZCHPcA (ORCPT ); Sun, 8 Mar 2009 11:32:00 -0400 In-Reply-To: <49B3E29F.1080400@codemonkey.ws> Sender: kvm-owner@vger.kernel.org List-ID: Anthony Liguori wrote: > Avi Kivity wrote: >> Anthony Liguori wrote: >>> Hi, >>> >>> I'd like to announce the creation of a QEMU stable branch based on >>> the recent 0.10.0 release. You can access it via anonymous SVN via: >>> >>> svn co svn://svn.savannah.nongnu.org/qemu/branches/stable_0_10_0 >>> >>> The stable branch will receive bug fixes from trunk until at least >>> the next major release. If submitting a bug fix, please consider >>> also testing the patch against stable and sending multiple patches >>> if appropriate. Using a tag in the subject line like [STABLE] would >>> also be helpful to indicate to the maintainers that a patch should >>> be considered for the stable tree. >>> >>> As the stable tree accumulates fixes, we'll make new stable releases >>> from the tree. >>> >> >> Will a stable release be called 0.10.0.1 or 0.10.1? (I'd prefer the >> latter) > > I was thinking the later but am open to suggestion. In this case, the branch ought to be called stable_0_10, no? -- error compiling committee.c: too many arguments to function