Hi, > > Yes. That may be. But there are a lot of bugfixes in the latest > > STABLE-snapshot I tested (26/07/02) - or exactly: All bugs I experienced > > were fixed. So the easiest thing would be to cancel all new > > features that were planned for 4.2.3 and move them to 4.3.0 and apply all > > patches that have been fixed in the last STABLE-snapshot and do a quick > > release process (no new features, no or at least few new problems). > > The use the snapshot for your production box...
That is no solution for the real problem. People are frustrated because they don't know if their software runs on the next machine they put it on because this machine maybe has another PHP-version. It's the same thing like GD or Apache 2. Why was GD forked by PHP, why was Apache 2-SAPI development stopped for a long time? Because it was unsatisfying. What does the license say about forking PHP? Regards, Sebastian Nohn -- +49 170 471 8105 - [EMAIL PROTECTED] - http://www.nohn.net/ PGP Key Available - Did I help you? Consider a gift: http://www.amazon.de/exec/obidos/wishlist/3HYH6NR8ZI0WI/ -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
