From: "Richard W.M. Jones" <rjones@redhat.com>
To: "Justin M. Forbes" <jmforbes@linuxtx.org>
Cc: qemu-devel@nongnu.org, qemu-stable@nongnu.org
Subject: Re: [Qemu-devel] Qemu stable releases
Date: Fri, 9 Dec 2011 12:01:20 +0000 [thread overview]
Message-ID: <20111209120120.GB20394@amd.home.annexia.org> (raw)
In-Reply-To: <20111209103937.GA20394@amd.home.annexia.org>
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 ..."
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.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
virt-df lists disk usage of guests without needing to install any
software inside the virtual machine. Supports Linux and Windows.
http://et.redhat.com/~rjones/virt-df/
next prev parent reply other threads:[~2011-12-09 12:01 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 [this message]
2011-12-09 13:25 ` Anthony Liguori
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=20111209120120.GB20394@amd.home.annexia.org \
--to=rjones@redhat.com \
--cc=jmforbes@linuxtx.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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).