mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Al Boldi <a1426z@gawab.com>
To: linux-kernel@vger.kernel.org
Subject: Re: A proposal; making 2.6.20 a bugfix only version.
Date: Thu, 9 Nov 2006 07:57:48 +0300	[thread overview]
Message-ID: <200611090757.48744.a1426z@gawab.com> (raw)

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


             reply	other threads:[~2006-11-09  4:55 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-09  4:57 Al Boldi [this message]
2006-11-09 17:05 ` Stephen Hemminger
2006-11-10 15:52   ` Al Boldi
2006-11-10 16:16     ` Jesper Juhl
2006-11-10 16:42       ` Stephen Hemminger
2006-11-10 16:53         ` Randy Dunlap
2006-11-10 19:33           ` Al Boldi
2006-11-10 19:49             ` Arjan van de Ven
2006-11-10 21:22               ` Al Boldi
2006-11-10 21:31                 ` Stephen Hemminger
2006-11-11  4:15                   ` Al Boldi
2006-11-11  5:09                     ` Stephen Hemminger
2006-11-11  7:23                       ` David Miller
2006-11-11 11:15                         ` Al Boldi
2006-11-11  6:31                     ` Valdis.Kletnieks
2006-11-11 11:15                       ` Al Boldi
2006-11-11  7:15           ` Willy Tarreau
2006-11-11 12:03             ` Neil Brown
2006-11-11 21:08               ` bugzilla (was Re: A proposal; making 2.6.20 a bugfix only version.) Pavel Machek
2006-11-11 19:16           ` A proposal; making 2.6.20 a bugfix only version Krzysztof Halasa
2006-11-11 19:15         ` Adrian Bunk
  -- strict thread matches above, loose matches on Subject: below --
2006-11-08 22:09 Jesper Juhl
2006-11-08 22:22 ` Arjan van de Ven
2006-11-08 22:40   ` Jesper Juhl
2006-11-08 23:05     ` Andreas Mohr
2006-11-08 23:54       ` Jan Engelhardt
2006-11-10 15:15     ` Pavel Machek
2006-11-10 15:48     ` Horst H. von Brand
2006-11-15 21:04       ` Jesper Juhl
2006-11-08 22:51   ` Andrew Morton
2006-11-09  9:26     ` Arjan van de Ven
2006-11-09  9:36       ` Andrew Morton
2006-11-09  9:52         ` Arjan van de Ven
2006-11-09 19:12           ` Andrew Morton
2006-11-09 19:21             ` Arjan van de Ven
2006-11-09 21:11               ` Adrian Bunk
2006-11-09 21:31                 ` Arjan van de Ven
2006-11-09 23:56                   ` Thomas Gleixner
2006-11-10  0:18                     ` Andrew Morton
2006-11-10 17:45                     ` Stefan Richter
2006-11-11 11:00                     ` Martin J. Bligh
2006-11-08 23:28   ` Diego Calleja
2006-11-09  6:48     ` Arjan van de Ven
2006-11-09 12:45       ` Rolf Eike Beer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200611090757.48744.a1426z@gawab.com \
    --to=a1426z@gawab.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®