lkml.org 
[lkml]   [2005]   [Jan]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: starting with 2.7
Date
On 4 Jan 2005, at 14:27, Horst von Brand wrote:

> Felipe Alfaro Solana <lkml@mac.com> said:
>
> [...]
>
>> Gosh! I bought an ATI video card, I bought a VMware license, etc.... I
>> want to keep using them. Changing a "stable" kernel will continuously
>> annoy users and vendors.
>
> If you are sooo attached to this, just keep a distribution for which
> vendors give you drivers. But when the vendor decides the product has
> to
> die to get you to buy the next "completely redone" (== minor fixes and
> updates) version, you are stranded for good.
>
>> I think new developments will force a 2.7 branch: when 2.6 feature set
>> stabilizes, people will keep more time testing a stable, relatively
>> static kernel base, finding bugs, instead of trying to keep up with
>> changes.
>
> And when 2.7 opens, very few developers will tend 2.6; and as 2.7
> diverges
> from it, fewer and fewer fixes will find their way back. And so you
> finally
> get a rock-stable (== unchanging) 2.6, but hopelessly out of date and
> thus
> unfixable (if nothing else because there are no people around who
> remember
> how it worked).

I can see no easy solution for this... If Linus decides to fork off
2.7, development efforts will go into 2.7 and fixes should get
backported to 2.6. If Linus decides to stay with 2.6, new development
will have to be "conservative" enough not to break things that were
working.

I tend to prefer forking off 2.7: more agressive features can be
implemented and tested without bothering disrupting the stable 2.6
branch.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 14:09    [from the cache]
©2003-2011 Jasper Spaans