[lkml]   [2004]   [Oct]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: My thoughts on the "new development model"
Hi Adrian,

On Sat, Oct 23, 2004 at 03:40:04AM +0200, Adrian Bunk wrote:

> 2.6.9 -> 2.6.10-rc1:
> - 4 days
> - > 15 MB patches

I firmly agree, and that's one of the reasons I still don't use 2.6. This
could be avoided with a shorter release cycle with far less new features
for each version (a bit like openbsd does), because about every maintainer
would have a valid base to work on for the next release or the one after,
and would not try to push unstable code in the "stable" kernel. Today, lots
of people are certain that 2.8 (or 3.0) won't be out before 3 or 4 years. So
if they want their code released soon, they push it hard in the current
mainline :-(

> It's a bit optimistic to call this amount of change "stabilizing".

What really frightens me is that judging from the changelogs, it really
looks like cleanups, bug fixes and sometimes core changes... This gives
a terrible idea of previous release code !

> 2.6 is corrently more a development kernel than a stable kernel.

That's how I present it to friends and customers too ;-) To others, I simply
say that it's the new stable kernel, and I observe how it works for them :-)

> The last bug I observed personally was the problem with suspending when
> using CONFIG_REGPARM=y together with Roland's waitid patch which was
> added in 2.6.9-rc2. If I'd used 2.6.9 with the same .config as,
> this was simple one more bug...

Each time I try a new release, I barely find it extremely slow and unstable,
and I don't know where to start from to report broken things... Unfortunately
I don't have enough time to spend on bug reports these days so I stick to a
stable 2.4.

> IMHO Andrew+Linus should open a short-living 2.7 tree soon and Andrew
> (or someone else) should maintain a 2.6 tree with less changes (like
> Marcelo did and does with 2.4).

Yes, but not until the core is stabilized. Otherwise, ever changing features
and exports will discourage driver maintainers from backporting fixes.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 14:07    [W:0.218 / U:29.772 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site