LWN.net Logo

Proposed stable release changes

From:  Greg KH <gregkh-AT-linuxfoundation.org>
To:  Linus Torvalds <torvalds-AT-linux-foundation.org>, Andrew Morton <akpm-AT-linux-foundation.org>, stable <stable-AT-vger.kernel.org>, lwn-AT-lwn.net
Subject:  Proposed stable release changes
Date:  Tue, 20 Aug 2013 15:40:32 -0700
Message-ID:  <20130820224032.GA20491@kroah.com>
Cc:  Guenter Roeck <linux-AT-roeck-us.net>, Hugh Dickins <hughd-AT-google.com>, Johannes Berg <johannes-AT-sipsolutions.net>, Borislav Petkov <bp-AT-alien8.de>, Linux Kernel Mailing List <linux-kernel-AT-vger.kernel.org>
Archive-link:  Article, Thread

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?

thanks,

greg k-h


(Log in to post comments)

Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds