From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:35526) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TbHmF-0008EN-Eq for qemu-devel@nongnu.org; Wed, 21 Nov 2012 16:24:12 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TbHmD-0002Lp-0S for qemu-devel@nongnu.org; Wed, 21 Nov 2012 16:24:11 -0500 Sender: fluxion Date: Wed, 21 Nov 2012 15:23:59 -0600 From: mdroth Message-ID: <20121121212358.GA16411@vm> References: <20121120161409.GA14974@vm> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [Qemu-devel] [ANNOUNCE] QEMU 1.2.1 Stable released List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Doug Goldstein Cc: qemu-devel@nongnu.org, qemu-stable@nongnu.org On Wed, Nov 21, 2012 at 01:55:07PM -0600, Doug Goldstein wrote: > On Tue, Nov 20, 2012 at 10:14 AM, mdroth wrote: > > Hi everyone, > > > > I am pleased to announce that the QEMU v1.2.1 stable release is now > > available at: > > > > http://wiki.qemu.org/download/qemu-1.2.1.tar.bz2 > > > > The official stable-1.2 repository has also been updated to v1.2.1: > > > > http://git.qemu.org/?p=qemu-stable-1.2.git;a=summary > > > > Will you be pushing fixes as they become approved on qemu-stable into > that tree's master? It'd be beneficial from a testing stand point. Agreed, but I don't push to them to the master branch, as patches need to pass a final round of testing before they get committed there. In the past I've used a seperate staging tree on github, and linked to it in periodic digests to qemu-stable. I tend to do these in bi-monthly batches as there's a round of testing before those go in as well. Currently I publish those here: https://github.com/mdroth/qemu/commits/stable-1.2-staging And eventually: https://github.com/mdroth/qemu/commits/stable-1.3-staging and so on. If something more "official", like a published qemu.org staging branch on qemu.org, seems worthwhile I can look into mirroring there. But expect the above github branches to be kept up-to-date in the meantime and afterward until otherwise stated. Keep in mind these are snapshot branches and may rebase from time to time (if issues pop up in later testing, for instance). > > > Thanks. > -- > Doug Goldstein >