08-22-2013, 11:35 AM
Registered: Jun 2000
Distribution: Debian, Red Hat, Slackware, Fedora, Ubuntu
Is the Stable Linux Kernel Moving Too Fast?
From a Linux Kernel mailing List debate
sparked by the stable Linux 3.10 kernel being updated twice in a day:
On Wed, Aug 21, 2013 at 11:20 AM, Stephen Warren <email@example.com> wrote:
> On 08/20/2013 04:40 PM, Greg KH wrote:
> Presumably the idea is that much useful testing only happens on -rc
> kernels rather than linux-next or arbitrary points in Linus' tree.
Linux-next gets little to no testing outside of compiles.
And I don't think the -rc releases are all that important either. The important part is to _wait_. Not "wait for an -rc". There are reasonable number of developers and users who actually run git kernels, just because they want to help. At rc points, you tend to get a few more of those.
In contrast, when patches get moved from the development tree to stable within a day or two, that patch has gotten basically _no_ testing in some cases (or rather, it's been tested to fix the thing it was supposed to fix, but then there are surprising new problems that it introduces that nobody even though about, and wasn't tested for).
So I don't think "is in an rc release" is the important thing. I think "has been in the standard git tree for at least a week" is what we should aim for.
Will it catch all cases? Hell no. We don't have *that* many people who run git kernels, and even people who do don't tend to update daily anyway. But at least this kind of embarrassing "We found a bug within almost minutes of it hitting mainline" should not make it into stable.