Return-Path: Date: Sat, 24 Aug 2013 20:45:26 +0200 From: Stefan Richter To: Steven Rostedt Cc: Willy Tarreau , Josh Boyer , Greg KH , 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: <20130824204526.39a85312@stein> In-Reply-To: <20130821105459.0b392711@gandalf.local.home> References: <20130820224032.GA20491@kroah.com> <20130820235700.GA7209@kroah.com> <20130821134248.GB16493@home.goodmis.org> <20130821141725.GB20685@1wt.eu> <20130821105459.0b392711@gandalf.local.home> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: 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/