All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: "Richard W.M. Jones" <rjones@redhat.com>
Cc: "Justin M. Forbes" <jmforbes@linuxtx.org>,
	qemu-devel@nongnu.org, qemu-stable@nongnu.org
Subject: Re: [Qemu-devel] Qemu stable releases
Date: Fri, 09 Dec 2011 07:25:39 -0600	[thread overview]
Message-ID: <4EE20C53.8020807@codemonkey.ws> (raw)
In-Reply-To: <20111209120120.GB20394@amd.home.annexia.org>

On 12/09/2011 06:01 AM, Richard W.M. Jones wrote:
> On Fri, Dec 09, 2011 at 10:39:37AM +0000, Richard W.M. Jones wrote:
>> FWIW in libguestfs we have such a policy.  Every few weeks I evaluate
>> _all_ commits along the development branch and cherry pick those that
>> meet this policy back to the stable branch, followed by making a new
>> stable release.  Here is the policy:
>>
>> http://libguestfs.org/guestfs.3.html#libguestfs_version_numbers
>>    from "Our criteria for backporting changes are ..."

Out of curiosity, what's the commit rate for libguestfs and what's the release 
schedule?

I tried this years ago with QEMU and while it resulted in a very active stable 
branch, it was a huge amount of work, particularly as we got about half way 
through the next development cycle.

Regards,

Anthony Liguori

> For completeness, here is an example stable branch containing
> cherry-picked commits:
>
> http://fedorapeople.org/git/?p=rjones/public_git/libguestfs.git;a=log;h=refs/remotes/origin/stable-1.14
>
> Compare to the master branch to see which commits did and didn't make
> it in.
>
> Rich.
>

  reply	other threads:[~2011-12-09 13:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-05 20:08 [Qemu-devel] Qemu stable releases Justin M. Forbes
2011-12-06  9:27 ` Stefan Hajnoczi
2011-12-09 10:39 ` Richard W.M. Jones
2011-12-09 12:01   ` Richard W.M. Jones
2011-12-09 13:25     ` Anthony Liguori [this message]
2011-12-09 13:47       ` Richard W.M. Jones
2011-12-09 12:55 ` Andreas Färber
2011-12-09 13:24   ` Anthony Liguori
2011-12-09 13:50     ` Andreas Färber
2011-12-09 13:28   ` Justin M. Forbes

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=4EE20C53.8020807@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=jmforbes@linuxtx.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@nongnu.org \
    --cc=rjones@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.