qemu-stable
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-stable] [Qemu-devel] [ANNOUNCE] QEMU 1.2.1 Stable released


From: mdroth
Subject: Re: [Qemu-stable] [Qemu-devel] [ANNOUNCE] QEMU 1.2.1 Stable released
Date: Wed, 21 Nov 2012 15:23:59 -0600
User-agent: Mutt/1.5.21 (2010-09-15)

On Wed, Nov 21, 2012 at 01:55:07PM -0600, Doug Goldstein wrote:
> On Tue, Nov 20, 2012 at 10:14 AM, mdroth <address@hidden> 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
> 



reply via email to

[Prev in Thread] Current Thread [Next in Thread]