From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:40443) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Rkl9Q-0008WC-KK for qemu-devel@nongnu.org; Tue, 10 Jan 2012 18:30:45 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Rkl9P-0000LK-AA for qemu-devel@nongnu.org; Tue, 10 Jan 2012 18:30:44 -0500 From: "Justin M. Forbes" Date: Tue, 10 Jan 2012 17:30:33 -0600 In-Reply-To: <4F0C3E11.2070309@suse.de> References: <20120109180008.GB31963@linuxtx.org> <4F0C3E11.2070309@suse.de> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit Message-ID: <1326238235.28119.7.camel@paddy.linuxtx.org> Mime-Version: 1.0 Subject: Re: [Qemu-devel] [Qemu-stable] Last call for 1.0.1 stable release List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Andreas =?ISO-8859-1?Q?F=E4rber?= Cc: qemu-stable@nongnu.org, qemu-devel@nongnu.org On Tue, 2012-01-10 at 14:33 +0100, Andreas Färber wrote: > Justin, > > Am 09.01.2012 19:00, schrieb Justin M. Forbes: > > Due to the repository move, holidays and other bits, we are a bit late > > getting out the door, but I want to get qemu 1.0.1 stable release done this > > week. We have a number of patches, but if you are sitting on anything or > > close to finishing up something, please get all patches to > > qemu-stable@nongnu.org by Wednesday Jan 11th to give time for testing > > before the release is cut. > > Could you be a bit more verbose, please? Currently, judging by > http://git.qemu.org/?p=qemu-stable-1.0.git;a=summary (which seems to be > lacking a v1.0 tag), it seems like only a Malta fix is queued so far? > > I'm new to the stable business but my expectation is that patches are > cherry-picked to the stable branch, if qualified, once applied to > master. I haven't seen any "Thanks, applied to stable-1.0 branch" reply > lately, but you're pinning 1.0.1 to a date already, leading to 1.0.1 > getting either no testing (if you apply pending patches today/tomorrow) > or hardly any fixes (one applied 47 hours ago)... > The tree is currently updated with everything from my queue, and I have already started some testing with what we have. The expectation of patches by Wednesday means that no patches received after that day will be applied for 1.0.1 unless they are to fix a problem in what I have received. Anything else will be applied toward 1.0.2. Essentially we have to make a release, and there is a good bit of testing required for a release, so the tree has to freeze at some point for that to happen. Justin