Re: Linux 2.6.21

Willy Tarreau
2007-04-26T05:08:03Z

On Thu, Apr 26, 2007 at 06:08:06AM +0200, Adrian Bunk wrote:
> On Wed, Apr 25, 2007 at 08:29:28PM -0700, Linus Torvalds wrote:
> >...
> > So it's been over two and a half months, and while it's certainly not the
> > longest release cycle ever, it still dragged out a bit longer than I'd
> > have hoped for and it should have. As usual, I'd like to thank Adrian (and
> > the people who jumped on the entries Adrian had) for keeping everybody on
> > their toes with the regression list - there's a few entries there still,
> > but it got to the point where we didn't even know if they were real
> > regressions, and delaying things further just wasn't going to help.
> >...
>
>
> Number of different known regressions compared to 2.6.20 at the time
> of the 2.6.21 release:
> 14
>
> Number of different known regressions compared to 2.6.20 at the time
> of the 2.6.21 release that were first reported in March or earlier:
> 8
>
> Number of different known regressions compared to 2.6.20 at the time
> of the 2.6.21 release with patches available at the time of the 2.6.21
> release [1]:
> 3
>
> What I will NOT do:
> Waste my time with tracking 2.6.22-rc regressions.
>
>
> We have an astonishing amount of -rc testers, but obviously not the
> developer manpower for handling them.
>
> If we would take "no regressions" seriously, it might take 4 or 5 months
> between releases due to the lack of developer manpower for handling
> regressions. But that should be considered OK if avoiding regressions
> was considered more important than getting as quick as possible to the
> next two week regression-merge window.
>
> But releasing with so many known regressions is insulting for the many
> people who spent their time testing -rc kernels.

Adrian,

I understand your concerns, it's more and more common to see developers
considering their work is worthless. But it's not. You should see the
current development model as a pipeline. What you feed at the input can
take some time to reach the output, and if we wait for the whole pipeline
to flush, more crap gets released.

What is needed is a higher priority on fixes for known regressions. I
find your summary above more readable than the large lists of regressions.
I think that you should reply to Linus' announces with something that
short, starting from the known-with-patch, known-for-more-than-1-month,
and all-known-regressions. It may help Linus focus even more on those.
Also, while it will not prevent any release with regressions, at least
it will prevent such a stupid case of known regressions with patch
available.

Also, check how many regressions you have reported and which have been
fixed during the -rc stage. You'll see your work really was useful.

Maybe Linus should accept to dedicate -final to known regressions only,
to force a check in this area ? Whether or not all of them get fixed is
not the real problem, but at least we will not have any regressions with
pending patch unapplied !

Please do continue that task if you have the time to do so !

Thanks,
Willy