Re: Final version, RFC release process
| From: | Pierre Joye | Date: | Thu, 02 Jun 2011 11:03:40 +0000 |
| Subject: | Re: Final version, RFC release process | ||
| References: | 1 2 3 4 5 6 7 8 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-52754@lists.php.net to get a copy of this message | ||
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.
Cheers,
--
Pierre
@pierrejoye | http://blog.thepimp.net | http://www.libgd.org