lkml.org 
[lkml]   [2005]   [Jan]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: starting with 2.7
On Mon, Jan 03, 2005 at 10:18:47AM -0500, Rik van Riel wrote:
>> This is especially true when you are talking about really
>> big database servers and bugs that take weeks or months
>> to trigger.

On Mon, Jan 03, 2005 at 04:34:38PM +0100, Adrian Bunk wrote:
> If at this time 2.8 was already released, the 2.8 kernel available at
> this time will be roughly what 2.6 would have been under the current
> development model, and 2.6 will be a rock stable kernel.
> If it was possible to get the 2.7 cycle pretty short, this would give
> the advantages of the old development model without most of its'
> disadvantages.

But that cannot be. Splitting the developer base is guaranteed to
reduce the amount of critical examination and testing given to both
series of kernel versions.

Also, .com's have finite horizons and slow response times; dev kernels
are almost universally beyond them. A dedicated dev kernel with a short
development cycle guarantees that the entire corporate side will be
left out of the development cycle. And this is not speculation; even
the long dev cycles do similar, or are only given attention after their
huge freezes. If they're always too late for a slow-moving dev cycle a
fast-moving dev cycle is guaranteed to outrun them completely.


-- wli
-
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