On Mon, 2012-08-27 at 22:05 -0700, Greg KH wrote:
As part of one of the Linux kernel Summit discussions today, it was
brought up that after a kernel is released (for example 3.5), it's a bit
too late to be doing testing to see how well it is working out. The .0
release is usually a bit rough, and it takes until the .1 or .2 release
to get most major issues out of the way.
So, the kernel developers would like to get a wider range of testing,
and one thing proposed would be to have rolling distros switch their
kernel over a bit earlier to the new release than they had been doing.
Specifically, around the -rc5 point in time would be great. That way,
any reported regressions could be fixed sooner and get into the final .0
release for everyone to use.
Now this does place a bit of a larger burden on the users of those
distros to be diligent in reporting problems, and the distro engineers
to report the issues upstream as well, but it sounds like a reasonable
thing to try out.
So, for the next kernel release, I'm thinking of switching the kernel in
Tumbleweed over to 3.6 at the -rc5 timeframe. Does anyone strongly
object to this happening?
No strong objection, but a minor comment..
In practice, rc5 vs .0 probably won't make much difference at all, but
more users will be bitten, else the move was a failure. So this move
explicitly plans on users being bitten, detracting from Tumbleweed's
rolling ~stable allure, _evading_ developmental regression detection and
reporting duties being a major attractor to running rolling ~stable ;-)
To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org