Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751472Ab3HTW5O (ORCPT ); Tue, 20 Aug 2013 18:57:14 -0400 Received: from mail.linux-iscsi.org ([67.23.28.174]:38035 "EHLO linux-iscsi.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751105Ab3HTW5N (ORCPT ); Tue, 20 Aug 2013 18:57:13 -0400 Message-ID: <1377039840.32763.11.camel@haakon3.risingtidesystems.com> Subject: Re: Proposed stable release changes From: "Nicholas A. Bellinger" To: Greg KH Cc: Linus Torvalds , Andrew Morton , stable , lwn@lwn.net, Guenter Roeck , Hugh Dickins , Johannes Berg , Borislav Petkov , Linux Kernel Mailing List Date: Tue, 20 Aug 2013 16:04:00 -0700 In-Reply-To: <20130820224032.GA20491@kroah.com> References: <20130820224032.GA20491@kroah.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.4.4-1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1645 Lines: 40 On Tue, 2013-08-20 at 15:40 -0700, 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? Sounds like a reasonable tradeoff, as long as the 'please include this to stable ASAP' latency for critical fixes does not end up being too large.. --nab -- 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/