From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:54571) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RZ0SO-0000XQ-4q for qemu-devel@nongnu.org; Fri, 09 Dec 2011 08:25:45 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RZ0SM-0007QN-Px for qemu-devel@nongnu.org; Fri, 09 Dec 2011 08:25:44 -0500 Message-ID: <4EE20C53.8020807@codemonkey.ws> Date: Fri, 09 Dec 2011 07:25:39 -0600 From: Anthony Liguori MIME-Version: 1.0 References: <1323115683.6884.8.camel@fedora64.linuxtx.org> <20111209103937.GA20394@amd.home.annexia.org> <20111209120120.GB20394@amd.home.annexia.org> In-Reply-To: <20111209120120.GB20394@amd.home.annexia.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] Qemu stable releases List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Richard W.M. Jones" Cc: "Justin M. Forbes" , qemu-devel@nongnu.org, qemu-stable@nongnu.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. >