From: Anthony Liguori <aliguori@us.ibm.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
kvm-devel <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] Planning for the 0.11.0 release
Date: Tue, 23 Jun 2009 10:47:58 -0500 [thread overview]
Message-ID: <4A40F92E.1070108@us.ibm.com> (raw)
In-Reply-To: <f43fc5580906230809r40bd7a08ld7ca1a1e812ae2d@mail.gmail.com>
Blue Swirl wrote:
> 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?
>
No, but it's not too hard to make svn->git bridges.
Regards,
Anthony Liguori
--
Regards,
Anthony Liguori
next prev parent reply other threads:[~2009-06-23 15:48 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-22 23:57 Planning for the 0.11.0 release Anthony Liguori
2009-06-23 12:12 ` [Qemu-devel] " Avi Kivity
2009-06-23 15:09 ` Blue Swirl
2009-06-23 15:47 ` Anthony Liguori [this message]
2009-06-23 15:49 ` Avi Kivity
2009-07-09 8:27 ` Mark McLoughlin
2009-07-09 13:32 ` Anthony Liguori
2009-07-10 1:10 ` Markus Armbruster
2009-07-10 13:53 ` Anthony Liguori
2009-07-10 15:04 ` Jan Kiszka
2009-07-10 15:49 ` Anthony Liguori
2009-07-10 16:23 ` Jan Kiszka
2009-07-10 16:33 ` Anthony Liguori
2009-07-10 16:52 ` Jan Kiszka
2009-07-10 17:03 ` Anthony Liguori
2009-07-10 17:15 ` Jan Kiszka
2009-07-10 17:40 ` Paul Brook
2009-07-10 17:58 ` Anthony Liguori
2009-07-10 18:02 ` Jan Kiszka
2009-07-10 18:22 ` Paul Brook
2009-07-10 16:55 ` Kevin Wolf
2009-07-10 16:59 ` Anthony Liguori
2009-07-10 17:10 ` Kevin Wolf
2009-07-10 17:31 ` Anthony Liguori
2009-07-10 17:10 ` Christoph Hellwig
2009-07-10 17:12 ` Kevin Wolf
2009-07-10 18:26 ` Christoph Hellwig
2009-07-10 17:29 ` Anthony Liguori
2009-07-10 18:13 ` Christoph Hellwig
2009-07-10 18:29 ` Anthony Liguori
2009-07-10 17:06 ` Anthony Liguori
2009-07-12 8:31 ` Avi Kivity
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A40F92E.1070108@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=blauwirbel@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).