mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chuck Wolber <chuckw@quantumlinux.com>
To: Greg KH <gregkh@suse.de>
Cc: "Randy.Dunlap" <rdunlap@xenotime.net>,
	jmforbes@linuxtx.org, linux-kernel@vger.kernel.org,
	stable@kernel.org, zwane@arm.linux.org.uk, tytso@mit.edu,
	davej@redhat.com, torvalds@osdl.org, akpm@osdl.org,
	alan@lxorguk.ukuu.org.uk
Subject: Re: [patch 0/6] 2.6.14.7 -stable review
Date: Sat, 28 Jan 2006 23:11:14 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.63.0601282221400.7205@localhost.localdomain> (raw)
In-Reply-To: <20060129053458.GA9293@suse.de>

On Sat, 28 Jan 2006, Greg KH wrote:

> No, it's not a 6 month window, I released this because people sent us 
> patches that they said should go into the 2.6.14-stable tree.  And as 
> people complained so much on lkml that we were dropping the old kernels 
> too fast, I never thought that people would complain that we are 
> maintaining older stuff that people seem interested in...

Don't think of it as a complaint. I'm sorry if it came off that way. It's 
anyone's job if they want to maintain any kernel release as long as they 
see fit.

I guess it's how we want to define ourselves. Was I mistaken to think that 
the -stable team maintains -stable for the current patch release only? 


> And, as always, anyone is free to take on maintaining any of the 
> different kernel versions for as long as they wish.
> 
> Does that help?

Well, that's the way it's always been. We have a late model 2.5 kernel 
that we still maintain in a level C avionics device on Boeing jets. You'd 
be amazed at how stable a 2.5 kernel can be made ;)


> Man, people complain when you don't maintain older kernels, and they 
> complain when you do...

Nope, wasn't complaining. It was an attempt at a dialog to more clearly 
define our purpose (or perhaps my personal understanding of it) *AND* let 
other developers know what to expect of us. We can choose to take on as 
much or as little as we want. I personally am good with whatever everyone 
else is comfortable taking on. We should manage outside expectations 
though so you don't have to answer "why do you drop old kernels" questions 
on your own. 

Things have changed a lot with the 2.6 release series and -stable seems to 
me to be one of those growing pains that still isn't fully resolved. It's 
a blending between the traditional stable release maintainers and the more 
nimble release schedule these days. Can the -stable team fill the void, or 
do we limit our scope to certain patch releases?

..Chuck..


-- 
http://www.quantumlinux.com
 Quantum Linux Laboratories, LLC.
 ACCELERATING Business with Open Technology

 "The measure of the restoration lies in the extent to which we apply
  social values more noble than mere monetary profit." - FDR

  parent reply	other threads:[~2006-01-29  7:10 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20060128015840.722214000@press.kroah.org>
2006-01-28  2:17 ` Greg KH
2006-01-28  2:18   ` [patch 1/6] setting irq affinity is broken in ia32 with MSI enabled Greg KH
2006-01-28  2:18   ` [patch 2/6] [EBTABLES] Don't match tcp/udp source/destination port for IP fragments Greg KH
2006-01-28  2:18   ` [patch 3/6] [SPARC64]: Fix ptrace/strace Greg KH
2006-01-28  2:18   ` [patch 4/6] [SPARC64]: Fix sys_fstat64() entry in 64-bit syscall table Greg KH
2006-01-28  2:18   ` [patch 5/6] [NETFILTER]: Fix crash in ip_nat_pptp (CVE-2006-0036) Greg KH
2006-01-28  2:18   ` [patch 6/6] [NETFILTER]: Fix another crash in ip_nat_pptp (CVE-2006-0037) Greg KH
2006-02-08 12:35     ` Holger Eitzenberger
2006-02-10  4:47       ` [stable] " Greg KH
2006-02-10  4:57         ` Andrew Morton
2006-02-10  5:08           ` Greg KH
2006-02-10  8:07             ` Harald Welte
2006-01-29  4:30   ` [patch 0/6] 2.6.14.7 -stable review Chuck Wolber
2006-01-29  4:43     ` Justin M. Forbes
2006-01-29  4:52       ` Chuck Wolber
2006-01-29  4:57         ` Randy.Dunlap
2006-01-29  5:34           ` Greg KH
2006-01-29  6:09             ` Willy Tarreau
2006-01-29  7:36               ` Chuck Wolber
2006-01-29  7:11             ` Chuck Wolber [this message]
2006-01-29  7:58       ` Chuck Wolber
2006-01-29  4:45     ` Randy.Dunlap
2006-01-29  5:02       ` Chuck Wolber
2006-01-29  6:17         ` Willy Tarreau
2006-01-29  7:43           ` Chuck Wolber
2006-01-31 15:05         ` Krzysztof Halasa

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=Pine.LNX.4.63.0601282221400.7205@localhost.localdomain \
    --to=chuckw@quantumlinux.com \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=davej@redhat.com \
    --cc=gregkh@suse.de \
    --cc=jmforbes@linuxtx.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    --cc=stable@kernel.org \
    --cc=torvalds@osdl.org \
    --cc=tytso@mit.edu \
    --cc=zwane@arm.linux.org.uk \
    /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

all inboxes | Powered by JetHome®