linux-kernel - Re: Linux 3.12 released .. and no merge window yet .. and 4.0 plans?

lists.openwall.net		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 linux-hardening linux-cve-announce 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]

Message-ID: <CA+8MBbJeQNBo=W1Gu2bBDQ83e0r3Omc3FdJjjGbxrAi0NM61Ww@mail.gmail.com>
Date:	Sun, 3 Nov 2013 19:11:16 -0800
From:	Tony Luck <tony.luck@...il.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Linux 3.12 released .. and no merge window yet .. and 4.0 plans?

On Sun, Nov 3, 2013 at 4:10 PM, Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
> And the reason I mention "4.0" is that it would be a lovely time to do
> that. Roughly a years heads-up that "ok, after 3.19 (or whatever),
> we're doing a release with *just* fixes, and then that becomes 4.0".
>
> Comments?

Unless you are planning to kick out releases significantly faster
than you have over the past few years ... then "roughly a year"
and "3.19" don't really match up. 3.17 would be a better guess.

This means you are ignoring the Knuth-ites who think 3.14 should
be followed by 3.141, 3.1415, 3.14159 etc. :-)

What would the rules look like for a "fixes-only" release? With
no merge window of new stuff would you enforce a "nothing
except regressions" policy after -rcN (for N >=3).  That might
feel odd in a fixes release to tell someone that their fix isn't
going to be taken.  But we all want the fixes release to converge
quickly so we can return to "ooh shiny" stuff - so "too big,
too late" should probably still be the rule.

Perhaps all the bugs to be fixed need to be logged in
bugzilla.kernel.org with some "for 4.0" tag by the
start of this fixes window - then we'd have some bound
on the release criteria for 4.0?

-Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/