Re: RIP PHP 4?
| From: | David Coallier | Date: | Fri, 06 Jul 2007 16:09:12 +0000 |
| Subject: | Re: RIP PHP 4? | ||
| References: | 1 2 3 4 5 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-30533@lists.php.net to get a copy of this message | ||
On 7/6/07, Antony Dovgal <antony@zend.com> wrote:
On 06.07.2007 19:58, Rasmus Lerdorf wrote:Well the initial question was to drop it but not kill it, if there would be another vote for killing it completely, I am totally 100% for it. 21st century... moving on.When was the last time we did a PHP4-only bug fix? Doesn't matter, we still have many of PHP4-only reports which nobody is going to look in anyway. Also it wasn't that long ago: - Fixed bug #38798 (OpenSSL init corrected in php5 but not in php4). (Tony) My fear is that the impact of the no-more-support statement is hurt when we qualify it with the fact that nothing is really changing. Well, I explained what should change in the first place - no more PHP4 reports. If you're unable to reproduce it with PHP5 - sorry, we can't help you. I'd be more in favour of a statement that put a final death date on it which means no new releases of any sort. We could still say security-fixes only by the end of the year and then death by 08/08/08 or something like that.To me it means in the first place that we can add a canned answer to the bugtracker which would say "PHP4 is not supported anymore, install PHP5" and close all PHP4 only reports. So no bug-fixes, no releases except for ones fixing critical security problems. And even that should be ceased either in say.. 1 or 2 years.
Yup, that's exactly what I said in my e-mail. -- Wbr, Antony Dovgal -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php-- David Coallier, Founder & Software Architect, Agora Production (http://agoraproduction.com) 51.42.06.70.18