2009/6/4 Lukas Kahwe Smith <m...@pooteeweet.org>: > > On 03.06.2009, at 22:52, Andrei Zmievski wrote: > >> I don't want people here to assume that these notes are "decisions" >> necessarily. They reflect the consensus of the group that was at the meeting >> and we should still take up the unresolved or arguable issues on this list. >> But hopefully we have a more structured and outlined list of things that we >> can follow for PHP 5.4/6. There are a couple of items that were unclear from >> the original notes — looking at you, Liz Smith :) - so, those of you who >> remember the discussion, please fill them in. > > > To me its absolutely critical that we do not give the impression that the > next bigger update after 5.3 will be 5.4. The next big thing is 6.0. If we > do a 5.4 then it will come after 6.0, just like 4.4 to ease migration. But > it makes no sense to release 5.4 with forward compatibility stuff until we > know we really nailed 6.0.
I completely agree, we have already seen how much further 5.3's release process was extended by constant new proposals and in the middle namespaces, doing a 5.4 (before a 6.0.0 alpha/beta/rc) will most likely crease development in HEAD (again, again) and extend the development a year. 5.4 could be a considerable upgrade after the 6.0.0 release, 6.0.0 have already been delayed many years, I remember in Paris 2005 someone said something about an expected 6.0.0 alpha or similar within a half year. > > regards, > Lukas Kahwe Smith > m...@pooteeweet.org > > > > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > -- regrads, Kalle Sommer Nielsen ka...@php.net -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
