On Sat, Nov 22, 2014 at 6:56 PM, Zeev Suraski <z...@zend.com> wrote: > Ferenc, all, > > > > The RFC has provisions for making the 3rd and 4th milestones move as needed: > > > > “It's worth noting that the 3rd and 4th milestones will be quality > dependent. If we have evidence that suggests that PHP 7 isn't sufficiently > mature to go into the RC stage in June, or GA in October - we should of > course adjust the timeline accordingly, and not push out a half-baked > release. However, the goal would be to stick as much as possible to the > deadline of new going-into-7.0 RFCs, and strive to follow the timelines for > the 2nd and 3rd milestones as much as possible, to ensure an October 2015 > release of PHP 7.0.” > > > > This language attempts to balance the motivation to get PHP 7.0 out to > market as soon as possible, with the unwillingness to compromise on > quality. If we end up having to have 4 months of betas/RCs instead of 3 – > then we will… > > > > Zeev > > > > > > based on that I would say that our average beta+rc release number is around > 7, and sometimes the release for a beta/RC can be delayed, so I think that > having only 3 months for the beta+RC period is too optimistic, we should > make that into 4 months at least, we could either push out the ETA for GA > or move back the alpha period by a month. > > > > sorry if this seems to be nitpicking, just trying to put my experiences > into use.
Which is very valuable and pretty matches our experiences for all releases since 5.3 but 5.4.0 (only in time). That's why I strongly suggest to make a more realistic time plan and stick to it. Specific dates can or should be define later but the period (mid october f.e.) should be defined now. One week more when it is about fixing one last critical bug for an existing feature is perfectly OK, 1 month to actually finish a new feature may not be good, at all. Cheers, -- Pierre @pierrejoye | http://www.libgd.org -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
