From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx0b-00082601.pphosted.com ([67.231.153.30]:20515 "EHLO mx0b-00082601.pphosted.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751671AbaCTXwj (ORCPT ); Thu, 20 Mar 2014 19:52:39 -0400 Message-ID: <532B7FEE.5090708@fb.com> Date: Thu, 20 Mar 2014 19:55:26 -0400 From: Chris Mason MIME-Version: 1.0 To: WorMzy Tykashi , Chris Mason , Subject: Re: btrfs-progs tagged as v3.12 References: <20131125214534.8160.40797@ret.masoncoding.com> In-Reply-To: Content-Type: text/plain; charset="UTF-8"; format=flowed Sender: linux-btrfs-owner@vger.kernel.org List-ID: On 03/20/2014 07:36 PM, WorMzy Tykashi wrote: > On 25 November 2013 21:45, Chris Mason wrote: >> Hi everyone, >> >> I've tagged the current btrfs-progs repo as v3.12. The new idea is that >> instead of making the poor distros pull from git, I'll be creating >> tagged releases at roughly the same pace as Linus cuts kernels. >> >> Given the volume of btrfs-progs patches, we should have enough new code >> and fixes to justify releases at least as often as the kernel. Of >> course, if there are issues that need immediate attention, I'll tag a .y >> release (v3.12.1 for example). >> >> If the progs changes slow down, we might skip a version. But tracking >> kernel version numbers makes it easier for me to line up bug reports, >> mostly because I already devote a fair number of brain cells to >> remembering how old each kernel is. >> >> Just let me know if there are any questions. >> >> -chris > > Hi Chris, > > I don't know if there wasn't enough commits to justify a 3.13 release > (I noticed your integration branch stalled 7 weeks ago, so I assume > this is the case), but can we expect a 3.14 release shortly after > Linus tags the mainline kernel as such? > Yes, I'm redoing the integration branch off of Dave's latest, and started testing it earlier this week. We'll definitely have a 3.14. Thanks, Chris