Stanislav Malyshev wrote: >> I can certainly see value in a special case for including things in both >> 5.6 and 7.x, both before and after 7.0 is released, but the the case for >> backporting anything other than a genuine bug fix to 5.5.x right now >> seems fairly weak, as will the case for backporting to 7.0.x after 7.1.0 >> is released (by which point 5.6.x will presumably be in its >> security-only phase). > > That means right now any enhancement somebody would propose would be > just released somewhere towards the end of next year. And since nobody > switches instantly, especially to the next major, their timeframe to use > it would be something like 4-5 years. I would have zero motivation as a > userland developer to work on a small change like adding an option that > I could benefit from in 5 years maybe. Would you?
Have you considered developers targeting shared hosting? Working on an improvement they have to wait for five years to use it is most certainly annoying. However, introducing this feature in a revision might not really help them at all. -- Christoph M. Becker -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
