From: Alexandre Oliva <oliva@gnu.org>
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: Sun, 10 Nov 2013 02:13:20 -0200 [thread overview]
Message-ID: <ortxfksxlr.fsf@livre.home> (raw)
In-Reply-To: <CA+55aFwLkvSkparyvekdmMyvr6Srw1KkzTBp=_w0oQRWnPpJug@mail.gmail.com> (Linus Torvalds's message of "Sun, 3 Nov 2013 16:10:59 -0800")
On Nov 3, 2013, Linus Torvalds <torvalds@linux-foundation.org> wrote:
> we'll have 4.0 follow 3.19 or something like that.
> we could do a release with just stability and bug-fixes
> the reason I mention "4.0" is that it would be a lovely time to do
> that.
That sounds backwards. .0s are known for instability and major new
features that justify the major version number bump. A fixes-only
release would make more sense as a last breath of the 3.* series, before
(or even after?) 4.0 comes out.
One way this might work is with a shorter release cycle after 3.19, with
a fixes-only merge window, which would lead to a shorter stabilization
cycle than usual, a rock-solid 3.20 release at the end of that cycle,
during which new features would presumably have piled up for longer than
usual, so as to make for more new features in the subsequent merge
window, which would then justify a bump to 4.0.
The shorter cycle towards 3.20, which would make the 2 cycles towards
4.0 shorter than two usual cycles, may help relieve some of the pressure
to get features into 3.19, since the merge window for 4.0 won't be that
far off.
--
Alexandre Oliva, freedom fighter http://FSFLA.org/~lxoliva/
You must be the change you wish to see in the world. -- Gandhi
Be Free! -- http://FSFLA.org/ FSF Latin America board member
Free Software Evangelist Red Hat Brazil Compiler Engineer
prev parent reply other threads:[~2013-11-10 4:13 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
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 [this message]
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=ortxfksxlr.fsf@livre.home \
--to=oliva@gnu.org \
--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;
as well as URLs for NNTP newsgroup(s).