From: Anthony Liguori <anthony@codemonkey.ws>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] release date of qemu 0.9.2?
Date: Tue, 21 Oct 2008 10:24:58 -0500 [thread overview]
Message-ID: <48FDF44A.2010302@codemonkey.ws> (raw)
In-Reply-To: <200810211610.44261.paul@codesourcery.com>
Paul Brook wrote:
>> Personally, I'd like to see much more frequent releases (every 3-6
>> months). I'm okay with not having complete features (like the
>> dyngen->TCG conversion) or host regressions because I think there's
>> value in having releases regularly compared to feature based releases.
>>
>> What do other people think? I'd be willing to do the leg work of releases.
>>
>
> Cutting releases is the easy. Making sure the tree is in a suitable state to
> be released is the hard bit. Releases without good quality control are IMHO
> pointless.
>
Yeah, what I meant by leg work was doing deep testing and nagging people
to fix things up before a release. Cutting a release is very simple.
> Given the speed of qemu development, I think 3 months is way too short for a
> release cycle. You may as well just have everyone pull from SVN.
>
How do you feel about 6 months?
Regards,
Anthony Liguori
> Paul
>
next prev parent reply other threads:[~2008-10-21 15:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9C406059-EE5F-41E6-9B53-4256087E64E8@hotmail.com>
2008-10-21 4:19 ` [Qemu-devel] release date of qemu 0.9.2? C.W. Betts
2008-10-21 7:41 ` Laurent Desnogues
2008-10-21 11:32 ` Aurelien Jarno
2008-10-21 13:32 ` Anthony Liguori
2008-10-21 14:38 ` Thiemo Seufer
2008-10-21 14:51 ` Anthony Liguori
2008-10-21 14:56 ` Glauber Costa
2008-10-21 14:57 ` Jean-Christophe PLAGNIOL-VILLARD
2008-10-21 15:11 ` Glauber Costa
2008-10-21 15:10 ` Paul Brook
2008-10-21 15:24 ` Anthony Liguori [this message]
2008-10-21 15:49 ` Paul Brook
2008-10-21 16:23 ` Anthony Liguori
2008-10-21 16:49 ` Thiemo Seufer
2008-10-21 18:13 ` Glauber Costa
2008-10-21 15:50 ` Armin
2008-10-26 15:58 ` Andreas Färber
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=48FDF44A.2010302@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=paul@codesourcery.com \
--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).