Something just occurred to me that might satisfy both sides of the issue. What about the way Apache handles their versions of Apache (1.x and 2.x). That is to say; they haven't abandoned 1.3 (no surprise, as I think it still has the biggest install base). They simply maintain security related issues. ppl still continue to build modules for 1.3. ppl still continue to run/install it. Apache doesn't hide it in some back corner. Everybody's happy. Would this approach not be an acceptable "EOL" for PHP4?
People can still build it after it goes EOL, they just need to go to the php museum or use cvs to get old versions, AFAICS no-one is preventing that. Keeping it on the front page will be a mistake IMO. Software evolves and the only way to do it efficiently is to stop doing things the old way and use the new way. Maybe we should see if Microsoft will still release patches for Visual Basic 3? Lets just get on with dropping PHP 4 as agreed in the announcement (any idea when the announcement will be?). People that want to continue using PHP 4 are free to do so, while the rest of us get to move on, and whilst the hosts know if they want to have secure servers then they will need to start looking at migration, we have given them plenty (more than plenty possibly) of notice so they can also inform their customers to start reviewing their scripts, most of the open source scripts I have checked, have supported PHP 5 for a while now and those that don't either update or loose their install base. IMO discussing keeping php 4 alive forever is a waste of time. Regards Marco
