On Wed, Apr 29, 2015 at 12:24 PM, François Laupretre <franc...@php.net> wrote:
> > De : Pierre Joye [mailto:pierre....@gmail.com] > > > > I would suggest then to end the white card given with the php7 rfc > > +1 on this. How can we make it official ? How can we stop the changes > merged to the PHP 7 branch every day ? Start a 7.1 branch ? > > PHP-7 should be branched out soon, and the RMs should start call out people when somebody pushes destabilizing changes without prior consensus. Kalle already asked Dmitry and co about the status of any pending/in-progress optimizitation/refactoring they are doing, so we can focus on stabilization and bugfixes. For 5.6 we tried the following policy: alpha1 means no new RFCs can target the release, RFCs already under discussion/voting can be finished and merged before beta1, after tagging beta1 there are no more features coming in, only fixes. For PHP7 we had a previously voted on and accepted timeline ( https://wiki.php.net/rfc/php7timeline) which stated marc 15 as the last time for RFCs targetting php7, and as far as I can tell, everybody seemed to agree that any RFC targetting PHP7 has to be accepted before that date (I remember seeing people panic about the scalar type hints voting being too late and not being able to meet the deadline with the vote). I just now realized that this RFC was originally put under discussion before the said deadline, so depending on what others think about it I would be ok merging it considering that it is still a fairly low risk change. Zeev, as the author of the php7timeline, what do you think about merging this one? -- Ferenc Kovács @Tyr43l - http://tyrael.hu
