Re: RFD: Kernel release numbering

[Dave Jones <davej@redhat.com>]

On Thu, Mar 03, 2005 at 12:07:59PM -0500, Bill Rugolsky Jr. wrote:

 > IMHO, Jeff Garzik has made two very useful points in this thread:
 > 
 > 1. The number of changesets flowing towards the Linus kernel is accelerating,
 >    so the kernel developers should be trying to accelerate the merging process,
 >    not introducing delays.

If you accelerate the merging process, you're lowering the review process.
The only answer to get regressions fixed up as quickly as possible
(because prevention is nigh on impossible at the current rate, so
 any faster is just absurd), would be more regular releases, so that
they got spotted quicker.

 > Dave has been building "unstable" bleeding-edge Fedora kernels from
 > 2.6.x-rcM-bkN, as well as "test" kernels for Fedora updates;

Actually only rawhide (FC4-to-be) has been getting -rc-bk patches.
The FC2/FC3 updates have been release versions only, with -ac patches.
(and also some additional patches backing out bits of the -ac)
During a test cycle (Ie, after FC4test1 is released, but before FC4 gold)
is the only time Fedora users regularly test a -rc-bk tree.
This is part of the problem with rebasing the existing releases to
new kernels. It's shoving a largely untested codebase into a release
that was never tested in that combination. It's expected that some
stuff will break, but the volume of breakage is increasing as time goes on.
Even if _I_ stopped rebasing the Fedora kernel, some of our users
will still want to build and run the latest kernel.org kernel on their
FC2 boxes. We shouldn't be expecting them to have to rebuild half of
their userspace just because we've been sloppy and broke interfaces.

		Dave