lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sun, 10 Nov 2013 02:13:20 -0200
From:	Alexandre Oliva <>
To:	Linus Torvalds <>
Cc:	Linux Kernel Mailing List <>
Subject: Re: Linux 3.12 released .. and no merge window yet .. and 4.0 plans?

On Nov  3, 2013, Linus Torvalds <> 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
You must be the change you wish to see in the world. -- Gandhi
Be Free! --   FSF Latin America board member
Free Software Evangelist      Red Hat Brazil Compiler Engineer
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists