ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Sasha Levin <sasha.levin@oracle.com>,
	"ksummit-discuss@lists.linuxfoundation.org"
	<ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [CORE TOPIC] Issues with stable process
Date: Tue, 14 Jul 2015 11:46:23 +0100	[thread overview]
Message-ID: <20150714104623.GQ11162@sirena.org.uk> (raw)
In-Reply-To: <20150713210226.519dedfd@gandalf.local.home>

[-- Attachment #1: Type: text/plain, Size: 918 bytes --]

On Mon, Jul 13, 2015 at 09:02:26PM -0400, Steven Rostedt wrote:

> But I highly doubt that having them sit in next for two weeks would
> change that. Again, the code that the patches fix was already in next,
> and the original bug was never found there. What makes you think bugs
> in the fix patches will be any different?

Two weeks seems excessive but having them there for a -next build means
the automated stuff has a chance to kick in which is 90% of what -next
gives us in terms of quality.  The benefit does depend on how likely the
change is to be affected by system/platform/config specific issues.

Indeed depending on the bug having things forced to sit in -next for too
long can be a real problem - I've had people refusing to fix build
errors in Linus' tree for a week as they wanted things to cook in -next
which took out automated testing of Linus' tree (and anything that
merged it) for the duration.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  parent reply	other threads:[~2015-07-14 10:46 UTC|newest]

Thread overview: 83+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-11 16:12 Sasha Levin
2015-07-12 10:02 ` Geert Uytterhoeven
2015-07-12 13:32   ` Sasha Levin
2015-07-13  0:52     ` NeilBrown
2015-07-13  3:32       ` Andy Lutomirski
2015-07-13  4:27       ` Sasha Levin
2015-07-13  5:10         ` NeilBrown
2015-07-13 22:55           ` Rafael J. Wysocki
2015-07-13 18:21         ` Steven Rostedt
2015-07-13 18:51           ` Mark Brown
2015-07-15 14:52             ` Olof Johansson
2015-07-15 15:59               ` Guenter Roeck
2015-07-15 16:03               ` Greg KH
2015-07-15 16:15                 ` Sasha Levin
2015-07-15 16:40                   ` Greg KH
2015-07-15 19:34                     ` Josh Boyer
2015-07-15 21:21                     ` Sasha Levin
2015-07-15 22:34                       ` Greg KH
2015-07-15 22:40                         ` Sasha Levin
2015-07-16  3:36                           ` Greg KH
2015-07-17  0:52                             ` Rafael J. Wysocki
2015-07-16  9:06                   ` Zefan Li
2015-07-16 18:14                 ` Olof Johansson
2015-07-14  0:42           ` Sasha Levin
2015-07-14  1:02             ` Steven Rostedt
2015-07-14  2:00               ` Sasha Levin
2015-07-14  2:28               ` Jonathan Corbet
2015-07-14  3:48                 ` Stephen Rothwell
2015-07-14  7:14                 ` Geert Uytterhoeven
2015-07-14 11:03                 ` James Bottomley
2015-07-14 13:29                   ` Steven Rostedt
2015-07-14 20:17                     ` James Bottomley
2015-07-14 20:45                       ` Mark Brown
2015-07-14 22:12                       ` Steven Rostedt
2015-07-14 22:36                         ` Andy Lutomirski
2015-09-01  8:44                   ` Jani Nikula
2015-09-01 20:52                     ` Greg KH
2015-09-01 21:00                       ` Sasha Levin
2015-09-01 21:08                         ` Jiri Kosina
2015-09-01 22:47                           ` Sasha Levin
2015-09-02 10:10                         ` Luis Henriques
2015-07-16  0:53                 ` Rafael J. Wysocki
2015-07-16 11:50                   ` Mark Brown
2015-07-14  3:42               ` Stephen Rothwell
2015-07-14  7:03               ` Geert Uytterhoeven
2015-07-14 10:46               ` Mark Brown [this message]
2015-07-14 13:57                 ` Sasha Levin
2015-07-14 15:25                   ` Mark Brown
2015-07-14 15:32                     ` Sasha Levin
2015-07-14 15:38                       ` Steven Rostedt
2015-07-14 15:53                         ` Sasha Levin
2015-07-14 16:02                           ` Steven Rostedt
2015-07-14 19:30                             ` Sasha Levin
2015-07-14 19:38                               ` Steven Rostedt
2015-07-15  1:49                               ` NeilBrown
2015-07-15  2:09                                 ` Sasha Levin
2015-07-15  2:28                                   ` NeilBrown
2015-07-15 10:13                                     ` James Bottomley
2015-07-15 23:24                                       ` NeilBrown
2015-07-16  1:05                                         ` Andy Lutomirski
2015-07-16  1:43                                           ` Linus Torvalds
2015-07-16  1:25                                         ` Steven Rostedt
2015-07-16  9:19                                           ` James Bottomley
2015-07-16 12:33                                             ` Jonathan Cameron
2015-08-03  8:32                                             ` Fengguang Wu
2015-07-14 15:56                       ` Mark Brown
2015-07-14 19:01                         ` Sasha Levin
2015-07-14 19:18                           ` Geert Uytterhoeven
2015-07-14 19:31                             ` Sasha Levin
2015-07-15  9:26                               ` Jan Kara
2015-07-16 12:53                           ` Mark Brown
2015-07-13  9:22       ` Jan Kara
2015-07-13 20:51       ` Greg KH
2015-07-14  0:51         ` Sasha Levin
2015-07-14  2:46         ` NeilBrown
2015-07-15 19:41         ` Steven Rostedt
2015-07-15 20:14           ` James Bottomley
2015-07-12 15:01 ` Masami Hiramatsu
2015-07-13 10:15 ` Zefan Li
2015-07-13 16:12   ` Sasha Levin
2015-07-14 10:08     ` Zefan Li
2015-07-14 14:00       ` Sasha Levin
2015-07-15  0:01         ` Greg Kroah-Hartman

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=20150714104623.GQ11162@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=rostedt@goodmis.org \
    --cc=sasha.levin@oracle.com \
    /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