On Fri, Aug 15, 2014 at 11:25 AM, Derick Rethans <der...@php.net> wrote:
> On Fri, 15 Aug 2014, Andrea Faulds wrote: > > > I’ve kept putting this off, but given the current “move phpng to > > master” vote, I really can’t delay this any longer. > > > > It looks like PHP 7 is going to happen and phpng will be the base of > > that. While we could move straight to PHP 7 after the release of PHP > > 5.6, I think there is some merit in having one more 5.x release, > > namely 5.7, which would follow our usual release process and come out > > next year. > > Basically, you're wanting to give up hope on PHP 7 in one year *at the > moment it is started*... I think that's a pretty big mistake to do this > already. The momentum is here now, let's use it to get PHP 7 > ready—instead of bogging ourselves down with a PHP 5.7. > we don't have a single instance where we were able to deliver a minor release under a year, and I'm fairly sure that 7.0 will see more proposed features/changes as any previous minor, because there are stuff which can only happen in a major version. More changes(both in numbers and in impact) will need more time to stabilize, so I think that the one year roadmap for 7.0 is unrealistic. You seem to be arguing that 5.7 would pull away resources from 7.0, but I'm fairly sure that 5.7 would be the smallest of the 5.x minor versions for two reasons: we are getting better with not letting BC breaks slip in in minors plus working on a major version is much more interesting as you have less restrictions, so I think that 5.7 will/would be only to make the bed for 7.0, mostly introducing E_DEPRECATEDs and maybe a handfull of small features. I think that there is no reason to give up our current release policy and roadmap, and bet everything on PHP7, we don't lose anything with keeping 5.7. -- Ferenc Kovács @Tyr43l - http://tyrael.hu
