Hi,
the primary goal should be to encourage people to move to 5.4 as soon as
possible. The clear marketing message should be along the lines of "PHP
5.4 is the best version there is, it has all of 5.3's bug fixes and
additional improvements". We have to drive the 5.4 adoption.
I also don't think it's a "till that date all kinds of fixes and from
then on suddenly security only" thing. For one due to the fact that
there are always enough corner cases and for the second that regular bug
fixing will phase out naturally ("Oh this is such a corner case I won't
validate it on 5.3, rather spend time on the next bug"). If we force
developers too much to verify and fix on multiple trees they either
blindly commit without testing[1] or don't fix bugs at all. In the end
most contributors do this voluntarily for fun (or ego or ...).
So to sum it all up: I would prefer to promise security fixes only to
the outside (2 years if people here think that's a good time) and then,
as a group, agree to do additional bug fixing during that time.
johannes
[1] Remember the PHP 6 story: There were enough commits 1:1 from 5.2
applied which sometimes didn't even compile.
On Fri, 2012-03-02 at 13:34 +0100, Pierre Joye wrote:
> hi,
>
> It should have been done before 5.4.0 was out, but better late than never.
>
> I put together four options here:
>
> https://wiki.php.net/rfc/php53eol
>
> I'm in favor of option #1, as it gives enough time to our users to
> migrate by reducing the maintenance period to only one year.
>
> Suggestions or comments welcome,
>
> Cheers,
> --
> Pierre
>
> @pierrejoye | http://blog.thepimp.net | http://www.libgd.org
>
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
