From: Hans de Bruin <jmdebruin@xmsnet.nl>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 3.12 released .. and no merge window yet .. and 4.0 plans?
Date: Mon, 04 Nov 2013 21:12:53 +0100 [thread overview]
Message-ID: <5277FFC5.4040204@xmsnet.nl> (raw)
In-Reply-To: <CA+55aFwLkvSkparyvekdmMyvr6Srw1KkzTBp=_w0oQRWnPpJug@mail.gmail.com>
On 11/04/2013 01:10 AM, Linus Torvalds wrote:
>
...
>
> Anyway..
>
> Onto a totally different topic: we're getting to release numbers where
> I have to take off my socks to count that high again. I'm ok with
> 3.<low teens>, but I don't want us to get to the kinds of crazy
> numbers we had in the 2.x series, so at some point we're going to cut
> over from 3.x to 4.x, just to keep the numbers small and easy to
> remember. We're not there yet, but I would actually prefer to not go
> into the twenties, so I can see it happening in a year or so, and
> we'll have 4.0 follow 3.19 or something like that.
>
> Now, it's just a number (since we've long since given up on
> feature-related releases), and it's at least a year away, so why do I
> even mention it at all?
>
> The reason I mention it is because I've been mulling over something
> Dirk Hohndel said during LinuxCon EU and the kernel summit. He asked
> at the Q&A session whether we could do a release with just stability
> and bug-fixes, and I pooh-poohed it because I didn't see most of us
> having the attention span required for that
> (cough*cough*moronic*woodland creature*cough*cough).
I would not trust 4.0 as a bug free and stable kernel. Now 4.0.99 I
would trust. Almost that is. because some developer would have asked the
4.0.y maintainer to commit his one day old 4.x bugfix to the 4.0.y tree
before lots of people would have tested it.
The 4.0 would only force a stable kernel maintainer to choose that
kernel as his next stable tree. If he does not 4.0 has no meaning at all.
The 4.0 also does not solve another problem. Since the regression team
stopped tracking bugs nobody really knows how many bugs have been
forgotten or ignored. There needs to be some sort of feedback-loop to
force people to fix problems before they invent new ones. I do not think
a bug-fix round once every 20 releases will accomplice that
--
Hans
next prev parent reply other threads:[~2013-11-04 20:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-04 0:10 Linux 3.12 released .. and no merge window yet .. and 4.0 plans? Linus Torvalds
2013-11-04 3:11 ` Tony Luck
2013-11-04 6:25 ` Ingo Molnar
2013-11-04 19:08 ` Josh Boyer
2013-11-04 19:53 ` Geert Uytterhoeven
2013-11-07 4:40 ` Greg KH
2013-11-07 9:01 ` Ingo Molnar
2013-11-04 17:00 ` Alexander Holler
2013-11-04 19:49 ` Geert Uytterhoeven
2013-11-04 20:16 ` Alexander Holler
2013-11-04 23:02 ` Alexander Holler
2013-11-06 13:42 ` Keith Curtis
2013-11-07 10:17 ` Alexander Holler
2013-11-15 1:11 ` Keith Curtis
2013-11-04 20:05 ` Olof Johansson
2013-11-04 20:12 ` Hans de Bruin [this message]
2013-11-04 21:46 ` Linux 3.12 released " Jan Engelhardt
2013-11-05 5:06 ` Aldo Iljazi
2013-11-05 5:08 ` Alexander Holler
2013-11-04 21:57 ` Linux 3.12 released .. and no merge window yet " One Thousand Gnomes
2013-11-10 4:13 ` Alexandre Oliva
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=5277FFC5.4040204@xmsnet.nl \
--to=jmdebruin@xmsnet.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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