Re: Final version, RFC release process

On 2 June 2011 13:03, Pierre Joye <pierre.php@gmail.com> wrote: > On Thu, Jun 2, 2011 at 1:01 PM, Peter Lind <peter.e.lind@gmail.com> wrote: >> On 2 June 2011 12:40, Pierre Joye <pierre.php@gmail.com> wrote: >> >> *snip* >> >>> >>> No, it is the same that what we proposed. What we proposed is that >>> every release is actually a LTS release. What Ubuntu uses works fine >>> for distros given that it is a distro with an insane amount of totally >>> unrelated projects they distribute, and alternative repositories exist >>> for almost each of them. >>> >>> For a programming language, it is a totally different story. >>> >> >> That makes more sense - you were, however, arguing against random LTS >> releases which was rather confusing (there's a big difference between >> "every release is an LTS" and "all LTS releases are random" - those >> are not the only options). > > The randomness is about which release-features tuples would become a > LTS, that's something that can't apply well to a project like php. > It's hard to see how that would be any more or less random than now, given that it would still be a question of votes or consensus. Presumably, features would not be removed (unless they were bad for the language) and so they would still make it into LTS releases - the next one up. Anyway, I'll stop it here, as I doubt I'll convince you of anything (and vice versa). Just one thing to add: thanks for the work on PHP :) Much appreciated. Regards Peter -- <hype> WWW: plphp.dk / plind.dk LinkedIn: plind BeWelcome/Couchsurfing: Fake51 Twitter: kafe15 </hype>