From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Willy Tarreau <w@1wt.eu>, Josh Boyer <jwboyer@fedoraproject.org>,
Greg KH <gregkh@linuxfoundation.org>,
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: Sat, 24 Aug 2013 20:45:26 +0200 [thread overview]
Message-ID: <20130824204526.39a85312@stein> (raw)
In-Reply-To: <20130821105459.0b392711@gandalf.local.home>
On Aug 21 Steven Rostedt wrote:
> I guess the other question to ask is, how long does it take for a
> problem to appear after hitting mainline? If a problem is found in -rc4
> before -rc5 comes out, then this would be sufficient. But if the
> problem from -rc4 isn't found till -rc6 then that tells us something
> too.
The estimate of one or two RC periods applies to hardware/ workloads which
everyone has or which wasn't supported by the previous release. For less
widely used hardware/ workloads which has been supported for years already,
it's more like between 2.5 months ( = a mainline kernel release period)
and more than a year ( = two release periods of typical distributions).
--
Stefan Richter
-=====-===-= =--- ==---
http://arcgraph.de/sr/
next prev parent reply other threads:[~2013-08-24 18:46 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 [this message]
2013-08-21 13:48 ` Borislav Petkov
2013-08-21 17:08 ` Greg KH
2013-08-21 18:20 ` Stephen Warren
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=20130824204526.39a85312@stein \
--to=stefanr@s5r6.in-berlin.de \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=gregkh@linuxfoundation.org \
--cc=hughd@google.com \
--cc=johannes@sipsolutions.net \
--cc=jwboyer@fedoraproject.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lwn@lwn.net \
--cc=rostedt@goodmis.org \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=w@1wt.eu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.