From: "Glauber Costa" <glommer@gmail.com>
To: qemu-devel@nongnu.org, Thiemo Seufer <ths@networkno.de>
Subject: Re: [Qemu-devel] release date of qemu 0.9.2?
Date: Tue, 21 Oct 2008 13:11:49 -0200 [thread overview]
Message-ID: <5d6222a80810210811q5297c4f8x5cf221d099c4a91d@mail.gmail.com> (raw)
In-Reply-To: <20081021145758.GA32412@game.jcrosoft.org>
On Tue, Oct 21, 2008 at 12:57 PM, Jean-Christophe PLAGNIOL-VILLARD
<plagnioj@jcrosoft.com> wrote:
> On 09:51 Tue 21 Oct , Anthony Liguori wrote:
>> Thiemo Seufer wrote:
>>> Anthony Liguori wrote:
>>>
>>>> C.W. Betts wrote:
>>>>
>>>>> -----BEGIN PGP SIGNED MESSAGE-----
>>>>> Hash: SHA1
>>>>>
>>>>> When will qemu be given the status of 0.9.2? I was browsing the
>>>>> source code of the Qemu that ships with OpenSuSE and noticed that
>>>>> there are a lot of patches. It would probably be helpful if there
>>>>> was a release that didn't depend on GCC 4.
>>>>>
>>>>> Also, what targets still depend on dyngen? And is anyone working
>>>>> on porting them to TCG?
>>>>>
>>>> A lot of previously supported hosts are no longer supported with TCG.
>>>> I would think adding those hosts would be more important than
>>>> completing the TCG conversion before cutting a new release.
>>>>
>>>
>>> I disagree. The most important hosts are supported, the other hosts
>>> were largely experimental anyway, and getting rid of dyngen / gcc3
>>> is IMHO worth a release.
>>>
>>
>> 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.
> I agree with you I think that the kernel way of release is good and can be
> used for qemu
The kernel has too many -rcX , which I believe does not suit qemu well.
This is because of the size of the user and developer base. The merge window is
also something that we would have a hard time doing without a distribuited scm.
So, kernel + adaptations is fine.
--
Glauber Costa.
"Free as in Freedom"
http://glommer.net
"The less confident you are, the more serious you have to act."
next prev parent reply other threads:[~2008-10-21 15:12 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 [this message]
2008-10-21 15:10 ` Paul Brook
2008-10-21 15:24 ` Anthony Liguori
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=5d6222a80810210811q5297c4f8x5cf221d099c4a91d@mail.gmail.com \
--to=glommer@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=ths@networkno.de \
/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).