Andi Gutmans wrote:
I'd suggest something close to what Rasmus suggested:
a) We make a clear statement on PHP.net that at the end of the year we
plan to discontinue bug fixes for PHP 4 except for security fixes.
b) We will discontinue supporting PHP 4 on 8/8/8 (because it sounds good
and gives people about a year).
Gives a year? Nice. Suddenly we've got some kind of time machine here? :D
It's weird that people think of releases like the thing suddenly vanishes from
all servers it's installed on or it stops working altogether when we're just
saying that we drop support for it. I wish that WAS possible...but unfortunately
people still can install it from existing tar balls..and it will work just fine.
> I also suggest to move PHP 4 downloads to the museum. I suggest though
to make a clear visible link from php.net/downloads.php to the museum
and make a clear statement that PHP 4 has moved (I am sure there are
still many who look for it for application compatibiity reasons).
This to be done immediately?
A year may seem a long time but it isn't when a company has to port a
big application over. Also don't forget that one of the reasons so many
Again, the existing installation won't stop working or vanish anywhere on the
date we stop _support_ and don't release new versions of it.. :)
--Jani
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
