From: Glauber Costa <glommer@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Cutting a new QEMU release
Date: Tue, 3 Feb 2009 21:48:44 -0200 [thread overview]
Message-ID: <5d6222a80902031548t7f4ba690g47597aa3858163cf@mail.gmail.com> (raw)
In-Reply-To: <4988C98D.9050808@codemonkey.ws>
>>
>> I agree we should not care now about targets that are not here anymore.
>> But things that are important for the community should be taken with
>> care (and arm linux user mode is certainly a very important target).
>>
>
> If someone is actively fixing it, then I'm perfectly happy to wait. If it's
> a known issue that noone is resolving, I don't think delaying a release
> helps anyone. However, documenting all of these things somewhere so that
> they are clearly visible may make it easier for someone to fix so the
> process of going through a release would probably be helpful in general.
>
We also have to take into account that making a release is likely to increase
the quality of qemu code base as a whole. Just because any user getting into
qemu site today, or getting code from a distro, is likely to be using
something very
old. Old enough that any bug reports will be probably useless to us.
Bug reports against 0.9.1 has happened many times already in the list.
--
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:[~2009-02-03 23:48 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-03 20:48 [Qemu-devel] Cutting a new QEMU release Anthony Liguori
2009-02-03 20:58 ` Glauber Costa
2009-02-03 21:35 ` Laurent Desnogues
2009-02-03 21:50 ` Anthony Liguori
2009-02-03 22:05 ` Laurent Desnogues
2009-02-03 22:47 ` Anthony Liguori
2009-02-03 23:48 ` Glauber Costa [this message]
2009-02-04 13:09 ` Ulrich Hecht
2009-02-04 0:31 ` David Turner
[not found] ` <74222928-D24B-4780-BDB0-D537A83C4F68@hotmail.com>
2009-02-04 5:08 ` C.W. Betts
2009-02-03 21:48 ` Rick Vernam
2009-02-03 22:07 ` Daniel P. Berrange
2009-02-04 14:50 ` Aurelien Jarno
2009-02-04 15:23 ` Tristan Gingold
2009-02-04 15:43 ` Lennart Sorensen
2009-02-04 16:01 ` Tristan Gingold
2009-02-04 18:17 ` [Qemu-devel] " Consul
2009-02-04 17:39 ` [Qemu-devel] " Blue Swirl
2009-02-04 17:50 ` Jonathan Kalbfeld
2009-02-04 20:07 ` Blue Swirl
2009-02-07 14:15 ` Stuart Brady
2009-02-04 15:58 ` Glauber Costa
2009-02-07 15:29 ` Shin-ichiro KAWASAKI
2009-02-11 21:49 ` Rob Landley
2009-02-12 14:44 ` Shin-ichiro KAWASAKI
2009-02-12 21:08 ` Rob Landley
2009-02-12 21:44 ` Rob Landley
2009-02-09 12:43 ` Mark McLoughlin
2009-02-09 21:36 ` Anthony Liguori
2009-02-10 0:47 ` Rob Landley
2009-02-10 7:22 ` M. Warner Losh
2009-02-13 8:40 ` Riku Voipio
2009-02-13 9:59 ` Stefano Stabellini
2009-02-13 16:30 ` Jamie Lokier
2009-02-13 17:00 ` Anthony Liguori
2009-02-13 19:04 ` [Qemu-devel] [PATCH] Revert block-qcow2.c to kvm-72 version due to corruption reports Jamie Lokier
2009-02-14 22:23 ` Dor Laor
2009-02-15 2:20 ` Jamie Lokier
2009-02-14 23:13 ` Anthony Liguori
2009-02-15 2:01 ` Jamie Lokier
2009-02-15 4:09 ` Anthony Liguori
2009-02-15 15:42 ` Jamie Lokier
2009-02-15 18:19 ` Anthony Liguori
2009-02-15 18:34 ` Johannes Schindelin
2009-02-16 1:01 ` Anthony Liguori
2009-02-17 0:52 ` Jamie Lokier
2009-02-17 2:55 ` Anthony Liguori
2009-02-16 1:19 ` Anthony Liguori
2009-02-17 1:01 ` Jamie Lokier
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=5d6222a80902031548t7f4ba690g47597aa3858163cf@mail.gmail.com \
--to=glommer@gmail.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).