If we aren't able to fix a low-level problem in a year we most probably won't be able to fix it in two as well.
Also, the closer we are to release, the more feedback we get, and the more bugs are able to fix. Delaying release would just reduce the attention of the users. Thanks. Dmitry. On Tue, Oct 14, 2014 at 9:24 PM, Rasmus Lerdorf <ras...@lerdorf.com> wrote: > On 10/14/2014 10:14 AM, Stas Malyshev wrote: > > Hi! > > > >> IMO, AST, INT64, NG, Uniforme variables style is enough for a new > >> marjor version.. why we still need to wait? > > > > We don't need to just "wait", as sit and do nothing. We need to allocate > > time for other features. > > There are also quite a few really low-level changes in master right now. > It is going to take quite a bit of time to stabilize. For example, > something as basic as array iteration is inadvertently different: > > https://bugs.php.net/68215 > > PHP is a mature project with reams and reams of legacy code out there. > Every single change, no matter how small, is like throwing a hand > grenade in a lake. There is the initial explosion and chaos and then the > ripples that go on and on. Dealing with all these ripples takes a lot > more time than most people think. For people who think that 1 year from > now is slow and conservative, it really isn't. It is quite aggressive > given the number of really low-level changes that are already in master. > Even if we froze the tree today I expect it could stretch to close to a > year to stabilize. > > -Rasmus > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > >
