From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MJ7dA-0001lC-Pv
	for qemu-devel@nongnu.org; Tue, 23 Jun 2009 11:09:52 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MJ7dA-0001jl-3r
	for qemu-devel@nongnu.org; Tue, 23 Jun 2009 11:09:52 -0400
Received: from [199.232.76.173] (port=50306 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MJ7d9-0001jS-NU
	for qemu-devel@nongnu.org; Tue, 23 Jun 2009 11:09:51 -0400
Received: from fg-out-1718.google.com ([72.14.220.153]:34483)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <blauwirbel@gmail.com>) id 1MJ7d9-0007mA-AR
	for qemu-devel@nongnu.org; Tue, 23 Jun 2009 11:09:51 -0400
Received: by fg-out-1718.google.com with SMTP id e21so46501fga.8
	for <qemu-devel@nongnu.org>; Tue, 23 Jun 2009 08:09:50 -0700 (PDT)
MIME-Version: 1.0
In-Reply-To: <4A401A65.3080804@us.ibm.com>
References: <4A401A65.3080804@us.ibm.com>
Date: Tue, 23 Jun 2009 18:09:50 +0300
Message-ID: <f43fc5580906230809r40bd7a08ld7ca1a1e812ae2d@mail.gmail.com>
Subject: Re: [Qemu-devel] Planning for the 0.11.0 release
From: Blue Swirl <blauwirbel@gmail.com>
Content-Type: text/plain; charset=UTF-8
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: Anthony Liguori <aliguori@us.ibm.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>, kvm-devel <kvm@vger.kernel.org>

On 6/23/09, Anthony Liguori <aliguori@us.ibm.com> wrote:
> Hi,
>
>  It's getting to be about the time to start thinking about the 0.11.0
> release.  0.10.0 was released on March 2nd so following with the 6 month
> release cycle, that would put 0.11.0 at September 2nd.
>
>  Based on the experiences with the stable releases, here's what I'd
> recommend:
>
>  o On July 15th, fork master -> stable-0.11
>  o Change version to 0.10.90
>  o Release qemu-0.11.0-rc1
>  o Release additional -rcN releases every 1-2 weeks
>  o Introduce a new maintainer for stable-0.10 (via git pulls)
>  o At least 1 week before release, hopefully we'll have the final -rcN that
> we can then declare 0.11.0.

Sounds OK. I think OpenBIOS releases should follow similar schedule,
maybe even with matching SVN tags (1.1-rc1 for 0.11.0-rc1 etc).

>  I think we should really try hard to make these dates.  I only have a few
> things that I would like to see happen before forking stable-0.11.  Namely:
>
>  o Setup qemu.org infrastructure (git hosting, wiki)
>  o Setup qemu bug tracker (see next mail)
>  o Include all ROM source code in tree via git submodules.  This is a major
> headache for distributors and I think it's important to resolve before our
> next release.

I think this is great, but OpenBIOS still uses Subversion. Can git use
SVN submodules for example?