Skip to contentSkip to conversation

Kernel Releases

DISCUSSION Dan Kegel 4 participants 5 messages Nov 25, 2001

lore
Share & tools
lore

Dan Kegel

author
#0 lore raw
Quoted 12 lines · David Relson

With the recent problems, the working
versions tend to be the -pre1 or -pre2 releases, not the released one. With a bit of QA, I think we can have 2.4.x releases be the stable releases. Here's how...

When the kernel maintainer, now Marcelo for 2.4, is ready to release the next kernel, for example 2.4.16, I suggest he switch from "pre?" to "-rc1" (as in release candidate). A day or two with -rc1 will quickly show if it has a show stopper. If so, then the minor fixes (and nothing else) go into -rc2. A day or two ..., and either -rc3 appears or we have a stable release and 2.4.16 is ready to be released.

Quoted 3 lines

Let's go the extra distance and have the releases be usable, stable kernels! It's what users want and it's within the abilities of the developers to produce. Let's do it :-)

Hear, hear!

Also, Marcelo should get in touch with the nice folks at [email protected] and find out what sort of regression tests they will be running on his kernels. Perhaps he can wait for their feedback on the -rcX kernels before declaring them final. (Not that they would have found the 2.4.15 problem with their current tests, but they'll catch a few things.)

- Dan

#1 lore raw
Quoted 19 lines · Dan Kegel
Quoted 12 lines · David Relson

With the recent problems, the working
versions tend to be the -pre1 or -pre2 releases, not the released one. With a bit of QA, I think we can have 2.4.x releases be the stable releases. Here's how...

When the kernel maintainer, now Marcelo for 2.4, is ready to release the next kernel, for example 2.4.16, I suggest he switch from "pre?" to "-rc1" (as in release candidate). A day or two with -rc1 will quickly show if it has a show stopper. If so, then the minor fixes (and nothing else) go into -rc2. A day or two ..., and either -rc3 appears or we have a stable release and 2.4.16 is ready to be released.

Quoted 3 lines

Let's go the extra distance and have the releases be usable, stable kernels! It's what users want and it's within the abilities of the developers to produce. Let's do it :-)

Hear, hear!

Quoted 8 lines

Also, Marcelo should get in touch with the nice folks at [email protected] and find out what sort of regression tests they will be running on his kernels. Perhaps he can wait for their feedback on the -rcX kernels before declaring them final. (Not that they would have found the 2.4.15 problem with their current tests, but they'll catch a few things.)

- Dan

We will be running all the available tests (until that list gets too large to be possible) on each kernel the morning after it's released. That's including pre/test/flyingmonkey/whatever. The test requests after a kernel release are currently automatic.

The regression tests we have planned are the majority of the tests available under the Linux Test Project (sourceforge:LTP). We have not however finished setting these up for automation.

Marcelo is also already working with the lab on non-stp related projects.

QA on the Linux Kernel will happen. However just like everything else in the Linux world, it won't be what you are used to. (read: automatic bug submissions to the LK list will NOT happen.)

One potential issue for waiting for these tests to finish before moving on to the next release is the fact that while all the tests are /requested/ the morning after a kernel hits kernel.org, they may not finish for days. This is because of other tests in the queues from developers or tests that take longer than a single day to complete. My thoughts on this tend towards having a short set of tests that can be considered a "smoke test" on the kernel to verify a short list of basic QA items before the major tests are ordered against a kernel. This short list would catch most compile/boot issues as well as a limited range of driver problems and a decent number of kernel component performance areas. I see the potential to have the STP going in the background from the development effort and only becoming visible to the LK list when we find problems or other things worth commenting on. I don't see a benefit for the development effort to be driven or controlled by anything the QA process does or doesn't do.

It's a constant game of catch up and verification. But at least the tools are getting better.

-Nathan

#2 lore raw
Quoted 2 lines · Nathan Dabney

We will be running all the available tests (until that list gets too large to be possible) on each kernel the morning after it's released.

Have you been following the kbuild 2.5 developments[1]? Linus has agreed that this change will go in early in the 2.5 cycle, that will impact on all automated testing for 2.5. There will be both good and bad impacts, the bad is the initial changeover, the good is a much cleaner build process and the ability to build multiple configurations from a single source tree.

[1] http://sourceforge.net/projects/kbuild/

#3 lore raw
In reply to Nathan Dabney

On Sun, Nov 25, 2001 at 09:24:21PM +1100, Keith Owens wrote:

| Have you been following the kbuild 2.5 developments[1]?  Linus has
| agreed that this change will go in early in the 2.5 cycle, that will
| impact on all automated testing for 2.5.  There will be both good and
| bad impacts, the bad is the initial changeover, the good is a much
| cleaner build process and the ability to build multiple configurations
| from a single source tree.

Some of us have this ability with our own stuff already. I've been doing automated multi-config builds since 2.0. But it will be nice to not have to track a moving target anymore. There will be a bigger initial bump for some of us, but hopefully all the features will be in there.

Signature · 4 lines
-----------------------------------------------------------------
| Phil Howard - KA9WGN |   Dallas   | http://linuxhomepage.com/ |
| [email protected] | Texas, USA | http://phil.ipal.org/     |
-----------------------------------------------------------------
#4 lore raw
In reply to Nathan Dabney
Quoted 5 lines · Keith Owens
Quoted 2 lines · Nathan Dabney

We will be running all the available tests (until that list gets too large to be possible) on each kernel the morning after it's released.

Quoted 8 lines

Have you been following the kbuild 2.5 developments[1]? Linus has agreed that this change will go in early in the 2.5 cycle, that will impact on all automated testing for 2.5. There will be both good and bad impacts, the bad is the initial changeover, the good is a much cleaner build process and the ability to build multiple configurations from a single source tree.

[1] http://sourceforge.net/projects/kbuild/

Yes, we will be able to add another method for (auto) kernel configuration when this becomes an issue (hopefully RSN).

Currently the method we use to "sanitize" submitted kernel configs for our hardware is as reliable as you can get under CML1. It doesn't however, give us a good way to build multiple configurations.

-Nathan