Re: A proposal; making 2.6.20 a bugfix only version.

[Stephen Hemminger <shemminger@osdl.org>]

On Thu, 9 Nov 2006 07:57:48 +0300
Al Boldi <a1426z@gawab.com> wrote:

> Andreas Mohr wrote:
> > On Wed, Nov 08, 2006 at 11:40:27PM +0100, Jesper Juhl wrote:
> > > Let me make one very clear statement first: -stabel is a GREAT think
> > > and it is working VERY well.
> > > That being said, many of the fixes I see going into -stable are
> > > regression fixes. Maybe not the majority, but still, regression fixes
> > > going into -stable tells me that the kernel should have seen more
> > > testing/bugfixing before being declared a stable release.
> >
> > Nice theory, but of course I'm pretty sure that it wouldn't work
> 
> Agreed.
> 
> > (as has been said numerous time before by other people).
> >
> > You cannot do endless testing/bugfixing, it's a psychological issue.
> 
> Agreed.
> 
> > If you do that, then you end up with -preXX (or worse, -preXXX)
> > version numbers, which would cause too many people to wait and wait
> > and wait with upgrading until "that next stable" kernel version
> > finally becomes available.
> > IOW, your tester base erodes, awfully, and development progress stalls.
> 
> IMHO, the psycho-problem is that you cannot intertwine development and stable 
> in the same cycle.  In that respect, the 2.6 development cycle is a real 
> flop, as it does not allow for focus.  
> 
> And focus is needed to achieve stability.  
> 
> Think catch22...
> 
> 
> Thanks!
> 
> --
> Al

There are bugfixes which are too big for stable or -rc releases, that are
queued for 2.6.20. "Bugfix only" is a relative statement. Do you include,
new hardware support, new security api's, performance fixes.  It gets to
be real hard to decide, because these are the changes that often cause
regressions; often one major bug fix causes two minor bugs.

Interestingly, adding a new feature often causes no bugs in the rest
of the code, but it does increase the possible bug surface so most of
the problems related to feature X are bugs in feature X. 


-- 
Stephen Hemminger <shemminger@osdl.org>