From: Russell King <rmk@arm.linux.org.uk>
To: Rob Landley <landley@trommello.org>
Cc: Bill Davidsen <davidsen@tmr.com>, Adrian Bunk <bunk@fs.tum.de>,
Linux-Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [OKS] Kernel release management
Date: Thu, 4 Jul 2002 13:16:54 +0100 [thread overview]
Message-ID: <20020704131654.B11601@flint.arm.linux.org.uk> (raw)
In-Reply-To: <200207030718.g637I0L145202@pimout2-int.prodigy.net>; from landley@trommello.org on Tue, Jul 02, 2002 at 09:19:41PM -0400
On Tue, Jul 02, 2002 at 09:19:41PM -0400, Rob Landley wrote:
> Look at the pressure to get stuff into 2.4 when it's already in 2.5. Because
> 2.4 is what people are actually using, and 2.5 is really just for os
> development and testing (and general playing with) at this point.
If stuff in 2.5 wasn't soo broken (looking at IDE here) then more people
would be using it, and less people would be wanting the 2.5 features back
ported to 2.4. IMHO, at the moment 2.5 has a major problem. It is not
getting the testing it deserves because things like IDE and such like
aren't reasonably stable enough.
Some developers in the ARM community have been to use 2.4 because 2.5
IDE has been broken for soo long. Having initially based their
development on 2.5, then being forced to switch to 2.4, they're not
going to switch back to 2.5 unless there's a _really_ good reason to.
Fixing IDE isn't "a really good reason" as far as they are concerned.
If we're going to make the 2.5 freeze in October and IDE remains as
unstable as it has since 2.5.4-ish, the months^wyears after that are
going to be a rough ride, and it will take a long time to shake the
bugs out.
At OLS, I was suggesting to people that 2.6 might happen in the summer of
2003. I'm seriously considering moving that estimate to Christmas 2003
or first couple of months of 2004 now.
Feel free to prove me wrong in one and a half years time. 8)
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2002-07-04 12:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-01 18:25 [OKS] Kernel release management Bill Davidsen
2002-07-01 18:56 ` Adrian Bunk
2002-07-01 19:24 ` Justin M. Forbes
2002-07-02 15:13 ` Bill Davidsen
2002-07-03 1:19 ` Rob Landley
2002-07-03 11:10 ` Matt Bernstein
2002-07-04 12:16 ` Russell King [this message]
2002-07-06 12:45 ` Theodore Ts'o
2002-07-07 19:37 ` Bernd Eckenfels
2002-07-04 12:02 ` Russell King
2002-07-04 13:33 ` Bill Davidsen
2002-07-04 14:32 ` Russell King
2002-07-03 15:34 ` Dave Jones
2002-07-03 14:24 ` Rob Landley
2002-07-04 2:18 ` jw schultz
2002-07-04 12:21 ` Russell King
2002-07-06 12:17 ` Dave Jones
2002-07-04 3:44 ` Bill Davidsen
[not found] <Pine.LNX.3.96.1020702110848.27954D-100000@gatekeeper.tmr.com.suse.lists.linux.kernel>
[not found] ` <200207030718.g637I0L145202@pimout2-int.prodigy.net.suse.lists.linux.kernel>
[not found] ` <20020704131654.B11601@flint.arm.linux.org.uk.suse.lists.linux.kernel>
2002-07-04 13:35 ` Andi Kleen
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=20020704131654.B11601@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=bunk@fs.tum.de \
--cc=davidsen@tmr.com \
--cc=landley@trommello.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox