On 05.07.2018 at 17:25, Nikita Popov wrote: > On Thu, Jul 5, 2018 at 1:25 PM, Christoph M. Becker <cmbecke...@gmx.de> > wrote: > >> On 05.07.2018 at 13:05, Björn Larsson wrote: >> >>> Den 2018-07-05 kl. 12:17, skrev Nikita Popov: >>> >>>> As such, I think that this feature can only go into 7.3 if the release >>>> schedule is adjusted. Extending the schedule by another 2-week alpha >>>> cycle >>>> would be sufficient to land this proposal in PHP 7.3. Otherwise it will >>>> just have to wait a few years for the next applicable release (based on >>>> recent discussions, it's not entirely clear whether that would be PHP >> 7.4 >>>> or 8.0). >>> >>> Sounds like the RMs for 7.3 need to weigh in on this. >>> For me I think it's worthwhile delaying two weeks, +1. >> >> Is there any precendent for postponing feature freeze during the (late) >> alpha stage? > > This was done for the PHP 7.1 release at pretty much the same time (before > the beta1 release it was decided to go with another alpha instead), for > much the same reasons (pending RFCs, though I don't remember the > specifics). See https://externals.io/message/94330 for the announcement > mail.
Ah, thanks, Nikita! Considering this, I'm not against delaying beta1 for two weeks and having an alpha4, provided that we do not allow any new (i.e. not yet under discussion) RFC to target 7.3. Stas, what do you think? -- Christoph M. Becker -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
