Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751763Ab3HTX5D (ORCPT ); Tue, 20 Aug 2013 19:57:03 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:38888 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751379Ab3HTX5B (ORCPT ); Tue, 20 Aug 2013 19:57:01 -0400 Date: Tue, 20 Aug 2013 16:57:00 -0700 From: Greg KH To: Josh Boyer Cc: Linus Torvalds , Andrew Morton , stable , lwn@lwn.net, Guenter Roeck , Hugh Dickins , Johannes Berg , Borislav Petkov , Linux Kernel Mailing List Subject: Re: Proposed stable release changes Message-ID: <20130820235700.GA7209@kroah.com> References: <20130820224032.GA20491@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2186 Lines: 50 On Tue, Aug 20, 2013 at 07:40:49PM -0400, Josh Boyer wrote: > On Tue, Aug 20, 2013 at 6:40 PM, Greg KH wrote: > > Hi all, > > > > Given that I had to just revert a patch in the recent stable releases > > that didn't get enough time to "bake" in Linus's tree (or in -next), I > > figured it was worth discussing some possible changes with how "fast" I > > pick up patches for stable releases. > > > > So, how about this proposal: > > > > - I will wait for a -rc to come out with the patch in it before putting > > it into a stable release, unless: > > - the maintainer ACKs it, or sends it directly (like DaveM does > > for networking patches) > > - I have seen enough discussion about a patch to show that it > > really does fix something / is good / doesn't cause problems. > > - obviously safe, i.e. "add a device id" type thing. > > > > Given that we have -rc releases every week, except for the initial -rc1 > > release, I don't think this will really cause any major delays. > > > > Also, now that we are about to head into my busy "travel season", odds > > are, I'll be at least a week behind anyway, so this would probably start > > happening without an "official" change. It's been a boring summer, I've > > been able to keep up with the stable stuff really easily, causing > > problems like this :) > > > > Objections? Comments? > > I like this overall. The only thing I might change is "wait for -rc2" > for patches tagged with CC: stable that go in during the merge window. > It seems those are the ones that tend to bite us. Maintainers can always tag their patches to have me hold off until -rc2 for that. And, given the huge number of patches for stable that come in during the -rc1 merge window, there's no way I can get to them all before -rc2 comes out, so this will probably end up being the case for most of them anyway. thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/