All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Steven Rostedt <rostedt@goodmis.org>, Greg KH <greg@kroah.com>
Cc: Josh Boyer <jwboyer@fedoraproject.org>,
	lizf.kern@gmail.com, ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [CORE TOPIC] stable issues
Date: Mon, 05 May 2014 21:04:20 -0700	[thread overview]
Message-ID: <53685F44.3040305@roeck-us.net> (raw)
In-Reply-To: <20140505232010.26a67845@gandalf.local.home>

On 05/05/2014 08:20 PM, Steven Rostedt wrote:
> On Mon, 5 May 2014 15:33:24 -0700
> Greg KH <greg@kroah.com> wrote:
>
>
>> And as for announcing it ahead of time, I'm never going to do that
>> again, the aftermath was horrid of people putting stuff that shouldn't
>> be there.  Heck, when people know about what the enterprise kernels are
>> going to be, they throw stuff into upstream "early", so it's a
>> well-known pattern and issue.
>
> Perhaps you can announce that 3.X "might" be the LTS tree. And just as
> 3.X merge window opens, announce that 3.(X-1) is the new LTS tree. It
> would be too late to have people pushing "unfinished" code into the LTS.
>

After the first time this happens people would know or assume that
it is going to be 3.(X-1), and push the unfinished stuff into that
release. Then 3.(X-1) would be in such a bad shape that using it as
stable release would be a bad idea. And if 3.(X-1) doesn't make it,
you would have even more people push unfinished crap into 3.X.
Ultimately you would end up with two bad releases instead of one.

In other words, I don't think this kind of reverse psychology would work.

Guenter

  reply	other threads:[~2014-05-06  4:04 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-04 11:19 [Ksummit-discuss] [CORE TOPIC] stable issues Li Zefan
2014-05-04 12:04 ` Guenter Roeck
2014-05-04 12:54 ` Josh Boyer
2014-05-04 14:26   ` Guenter Roeck
2014-05-05  0:37     ` Josh Boyer
2014-05-05  3:09       ` Li Zefan
2014-05-05  3:47       ` Guenter Roeck
2014-05-05 11:31         ` Jason Cooper
2014-05-05 13:40           ` Guenter Roeck
2014-05-05  6:10       ` Michal Simek
2014-05-05  2:47   ` Li Zefan
2014-05-05 13:41     ` Theodore Ts'o
2014-05-05 15:23       ` Takashi Iwai
2014-05-05 15:39         ` Jan Kara
2014-05-05 16:02           ` Takashi Iwai
2014-05-05 16:07             ` Jason Cooper
2014-05-05 16:17               ` Takashi Iwai
2014-05-05 22:33       ` Greg KH
2014-05-06  3:20         ` Steven Rostedt
2014-05-06  4:04           ` Guenter Roeck [this message]
2014-05-06 10:49             ` Steven Rostedt
2014-05-05  3:22   ` Greg KH
2014-05-04 15:35 ` Ben Hutchings
2014-05-04 15:45   ` Guenter Roeck
2014-05-05  3:00   ` Li Zefan
2014-05-05  1:03 ` Olof Johansson
2014-05-07  2:49 ` Masami Hiramatsu
2014-05-07  2:58   ` Davidlohr Bueso
2014-05-07  8:27     ` Masami Hiramatsu
2014-05-07  8:39       ` Matt Fleming
2014-05-07 11:45         ` Masami Hiramatsu
2014-05-07 12:45           ` Daniel Vetter
2014-05-08  3:20             ` Masami Hiramatsu
2014-05-09 12:32               ` Daniel Vetter
2014-05-12  6:55                 ` Masami Hiramatsu
2014-05-13 20:36                   ` Steven Rostedt
2014-05-13 20:40                     ` Davidlohr Bueso
2014-05-14  1:30                     ` Masami Hiramatsu
2014-05-07 18:40       ` Davidlohr Bueso
2014-05-07  9:06     ` Dan Carpenter
2014-05-07 14:15       ` Jan Kara
2014-05-08  3:38         ` Li Zefan
2014-05-08  9:41           ` Jan Kara
2014-05-08 20:35             ` Andy Lutomirski
2014-05-09  4:11               ` Greg KH
2014-05-09  5:33                 ` Masami Hiramatsu
2014-05-09  5:41                   ` Greg KH
2014-05-07  3:05   ` Li Zefan
2014-05-07  3:31     ` Masami Hiramatsu
2014-05-07  7:20     ` Laurent Pinchart
2014-05-13 20:46     ` Steven Rostedt

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=53685F44.3040305@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=greg@kroah.com \
    --cc=jwboyer@fedoraproject.org \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=lizf.kern@gmail.com \
    --cc=rostedt@goodmis.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 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.