Everything
php
Learn Community Releases The PHP Project
Home » Project » Newsgroups » php.internals » 8.0 Feature Freeze in 4 weeks »

8.0 Feature Freeze in 4 weeks

php.internals

Sara Golemon

6 years ago
Per the timetable at https://wiki.php.net/todo/php80 , the PHP-8.0 branch will be cut in FOUR WEEKS on Aug 4th just prior to the release of php-8.0.0beta1 on Aug 6th. Please note that August 4th marks FEATURE FREEZE for 8.0. All RFCs currently in discussion targeting 8.0 should plan to begin voting in the next 2 weeks in order to have sufficient time to complete prior to the August 4th deadline and have their initial implementations merged before the branch is cut. All RFCs not yet in discussion... Well, tick tock, right? -Sara

Nikita Popov

6 years ago
On Tue, Jul 7, 2020 at 3:49 PM Sara Golemon <pollita@php.net> wrote:
> Per the timetable at https://wiki.php.net/todo/php80 , the PHP-8.0 branch > will be cut in FOUR WEEKS on Aug 4th just prior to the release of > php-8.0.0beta1 on Aug 6th. > Please note that August 4th marks FEATURE FREEZE for 8.0. > > All RFCs currently in discussion targeting 8.0 should plan to begin voting > in the next 2 weeks in order to have sufficient time to complete prior to > the August 4th deadline and have their initial implementations merged > before the branch is cut. > All RFCs not yet in discussion... Well, tick tock, right? > > -Sara >
Just so people aren't surprised, I plan to start landing implementations for RFCs that are likely to be accepted in advance of the actual vote closure, as we have many RFC votes ending close to feature freeze. Of course, if something ends up not passing, it will be reverted. Nikita

Sara Golemon

6 years ago
On Tue, Jul 21, 2020 at 9:29 AM Nikita Popov <nikita.ppv@gmail.com> wrote:
> Just so people aren't surprised, I plan to start landing implementations > for RFCs that are likely to be accepted in advance of the actual vote > closure, as we have many RFC votes ending close to feature freeze. Of > course, if something ends up not passing, it will be reverted. > > Sounds 100% reasonable, the two you have in voting phase are both looking
pretty solid. I'd rather have the hazard of a last-minute revert than a last-minute merge. -Sara

Benjamin Eberlei

6 years ago
On Tue, Jul 21, 2020 at 4:47 PM Sara Golemon <pollita@php.net> wrote:
> On Tue, Jul 21, 2020 at 9:29 AM Nikita Popov <nikita.ppv@gmail.com> wrote: > > > Just so people aren't surprised, I plan to start landing implementations > > for RFCs that are likely to be accepted in advance of the actual vote > > closure, as we have many RFC votes ending close to feature freeze. Of > > course, if something ends up not passing, it will be reverted. > > > > Sounds 100% reasonable, the two you have in voting phase are both looking > pretty solid. I'd rather have the hazard of a last-minute revert than a > last-minute merge. >
the namespace token one is also a requirement for the attribute syntax @@ patch, which also requires another review cycle afterwards, so this way it'll be a little less time pressed for that one.