qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: "Andreas Färber" <andreas.faerber@web.de>
Cc: Avi Kivity <avi@redhat.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] branch and tag names
Date: Sun, 26 Apr 2009 17:05:25 -0500	[thread overview]
Message-ID: <49F4DAA5.5040802@codemonkey.ws> (raw)
In-Reply-To: <8B2E6405-6772-474F-9B8F-DB1A1689CA2D@web.de>

Andreas Färber wrote:
>
> +1 for v0.10.2
>
> I don't see the point of having stable/0.10 though. Why do we need 
> multiple stable? stable will be branched as v0.10.x, then after the 
> last 0.10.x release, stable can be hard-reset to master and branched 
> as v0.11.x when ready, and so on.
>
> Btw, any plans of doing a pick-up branch now?

My current plan is to fork a stable/0.11 before the 0.11.0 release.  
We'll do a few release candidates before the final release and then the 
branch will keep living as the stable series.  I'll stop maintaining 
stable/0.10 after 0.11.0 but at that point but if someone else wants to 
maintain it (via periodic git pull requests),  I'm happy to let it live 
for as long as there is an active maintainer.

It's relatively easy too.  It's just a matter of watching what goes into 
stable/0.11 and cherry picking appropriately.  Any stable/0.10 specific 
bugs would have to be handled specially too but those should be very 
rare (hopefully).

I think it really makes most sense for folks that are maintaining 
something based on a stable branch because of a product (like an 
enterprise/lts distro release).  I expect that not every QEMU release 
will have a long lived stable branch but I expect some will.

Of course, we still have some time to figure this all out.  Based on 
0.10.x, I think we need about a month of stabilization for 0.11 so if we 
stick with 6 month releases, I'd expect stable/0.11 to branch out 
sometime in late June/early July.

Regards,

Anthony Liguori
> Andreas
>

  parent reply	other threads:[~2009-04-26 22:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-26 18:01 [Qemu-devel] branch and tag names Avi Kivity
2009-04-26 19:49 ` Anthony Liguori
2009-04-26 20:05   ` M. Warner Losh
2009-04-26 20:10   ` Andreas Färber
2009-04-26 21:02     ` M. Warner Losh
2009-04-26 22:05     ` Anthony Liguori [this message]
2009-04-27  6:33     ` Avi Kivity
2009-04-27 17:32       ` Andreas Färber
2009-04-27  6:32   ` Avi Kivity

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=49F4DAA5.5040802@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=andreas.faerber@web.de \
    --cc=avi@redhat.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).