From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LUV0Z-0002RN-15 for qemu-devel@nongnu.org; Tue, 03 Feb 2009 18:48:47 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LUV0Y-0002R9-AL for qemu-devel@nongnu.org; Tue, 03 Feb 2009 18:48:46 -0500 Received: from [199.232.76.173] (port=34067 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LUV0Y-0002R6-4s for qemu-devel@nongnu.org; Tue, 03 Feb 2009 18:48:46 -0500 Received: from qw-out-1920.google.com ([74.125.92.146]:30855) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LUV0X-0002Ui-RF for qemu-devel@nongnu.org; Tue, 03 Feb 2009 18:48:45 -0500 Received: by qw-out-1920.google.com with SMTP id 5so561693qwc.4 for ; Tue, 03 Feb 2009 15:48:44 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <4988C98D.9050808@codemonkey.ws> References: <4988AD96.6090308@codemonkey.ws> <5d6222a80902031258m59691fach7077f516f9b078df@mail.gmail.com> <761ea48b0902031335t71922b13ne2a22baa38318698@mail.gmail.com> <4988BC3E.8080305@codemonkey.ws> <761ea48b0902031405u59c6dce2y8f7db73759dbaf0f@mail.gmail.com> <4988C98D.9050808@codemonkey.ws> Date: Tue, 3 Feb 2009 21:48:44 -0200 Message-ID: <5d6222a80902031548t7f4ba690g47597aa3858163cf@mail.gmail.com> Subject: Re: [Qemu-devel] Cutting a new QEMU release From: Glauber Costa Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org >> >> 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."