> Users should be encouraged to update to PHP5 before all. It's not just > a marketing vehicle.
I am not advocating prolonging the use of PHP4. However, it is not a switch that can be flipped without carefully planning on consequences. For me, it is not only the migration of roundcube, but all of the PHP code we host, some of which has not been touched in years. Here, I am in the middle of many migrations, of which PHP4 to PHP5 is one. I simply need some breathing room for a few weeks to be able to properly test and manage our migration. I do not want to pull in a svn update that is not compatible with my _current_ environment, even though I am working to migrate that environment to PHP5. You may chid me for waiting so long, yes. However I have not been able to properly convince those that pay me how important this migration is. I keep getting TODO items added to my list _above_ the PHP version migration. We still have machines running Windows NT 3.5.1 on Alpha, if you want to talk about unsupported ;) I think it would be a good idea in the future to make a svn commit specifically labeled with the version number of a release. It was great to see the original post in this thread so that the demarcation line between PHP4 and PHP5 is clear. And it was clear on the SVN log. Not so much with the 0.1.1 release. Charles Dostale System Admin - Silver Oaks Communications http://www.silveroaks.com/ 824 17th Street, Moline IL 61265 _______________________________________________ List info: http://lists.roundcube.net/dev/
