public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	stable <stable@vger.kernel.org>,
	lwn@lwn.net, Guenter Roeck <linux@roeck-us.net>,
	Hugh Dickins <hughd@google.com>,
	Johannes Berg <johannes@sipsolutions.net>,
	Borislav Petkov <bp@alien8.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Proposed stable release changes
Date: Wed, 21 Aug 2013 12:20:07 -0600	[thread overview]
Message-ID: <521504D7.7090204@wwwdotorg.org> (raw)
In-Reply-To: <20130820224032.GA20491@kroah.com>

On 08/20/2013 04: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: [...]

Presumably the idea is that much useful testing only happens on -rc
kernels rather than linux-next or arbitrary points in Linus' tree.

If so, then don't you want to wait for two -rc releases to come out that
include the patch?

When the first -rc that contains the patch is released, people will test
it then. This won't happen immediately, but might take a few days.

By the time the second -rc that contains the patch is released, that's
presumably enough time for people to have tested the first -rc, and
hence we then presume the patch doesn't cause too many issues.

That's still only an average of 1.5 weeks delay, with a min-max of 1-2,
ignoring the merge window and assuming bugfix patches go quickly
upstream from subsystem maintainers.

  parent reply	other threads:[~2013-08-21 18:20 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-20 22:40 Proposed stable release changes Greg KH
2013-08-20 22:58 ` Willy Tarreau
2013-08-20 23:12   ` Greg KH
2013-08-20 23:57     ` Guenter Roeck
2013-08-21  5:24     ` Willy Tarreau
2013-08-20 23:04 ` Nicholas A. Bellinger
2013-08-20 23:12   ` Greg KH
2013-08-20 23:11 ` Guenter Roeck
2013-08-20 23:17   ` Greg KH
2013-08-21  0:11     ` Guenter Roeck
2013-08-21  0:42       ` Greg KH
2013-08-20 23:40 ` Josh Boyer
2013-08-20 23:57   ` Greg KH
2013-08-21  0:41     ` Josh Boyer
2013-08-21  0:49       ` Greg KH
2013-08-21  1:03         ` Josh Boyer
2013-08-21  1:11           ` Guenter Roeck
2013-08-21 18:15           ` Greg KH
2013-08-21  5:38         ` Willy Tarreau
2013-08-21 13:37           ` Steven Rostedt
2013-08-21 17:23             ` Jochen Striepe
2013-08-21 17:58               ` Steven Rostedt
2013-08-21 20:07                 ` Borislav Petkov
2013-08-21 20:16                   ` Greg KH
2013-08-21 21:00                     ` Borislav Petkov
2013-08-21 13:42       ` Steven Rostedt
2013-08-21 14:17         ` Willy Tarreau
2013-08-21 14:54           ` Steven Rostedt
2013-08-24 18:45             ` Stefan Richter
2013-08-21 13:48 ` Borislav Petkov
2013-08-21 17:08   ` Greg KH
2013-08-21 18:20 ` Stephen Warren [this message]
2013-08-21 18:36   ` Linus Torvalds
2013-08-21 20:00     ` Borislav Petkov
2013-08-21 20:54       ` Tony Luck
2013-08-22  8:57         ` Borislav Petkov
2013-08-22 10:59         ` Geert Uytterhoeven
2013-08-22  0:05     ` Stephen Rothwell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=521504D7.7090204@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=akpm@linux-foundation.org \
    --cc=bp@alien8.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=hughd@google.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lwn@lwn.net \
    --cc=stable@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox