Re: Re: [RFC] Deprecations for PHP 8.6
| From: | Gina P. Banyard | Date: | Mon, 20 Jul 2026 10:40:54 +0000 |
| Subject: | Re: Re: [RFC] Deprecations for PHP 8.6 | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-132042@lists.php.net to get a copy of this message | ||
On Monday, 13 July 2026 at 17:04, Gina P. Banyard <internals@gpb.moe> wrote:
>
> On Tuesday, 7 July 2026 at 12:54, Gina P. Banyard <internals@gpb.moe> wrote:
>
> > On Monday, 22 June 2026 at 14:13, Gina P. Banyard <internals@gpb.moe> wrote:
> >
> > > Hello internals,
> > >
> > > It is this time of year again where we proposed a list of deprecations to add in PHP
> > > 8.6:
> > >
> > > https://wiki.php.net/rfc/deprecations_php_8_6
> > >
> > > As a reminder, this list has been compiled over the course of the past year by
> > > different people.
> > >
> > > And as usual, each deprecation will be voted in isolation.
> > >
> > > We still have a bit of time anyone else to propose additional deprecations, and if
> > > you have write access feel free to add them directly to the RFC.
> > > Please note that with the new RFC policy rules the RFC must be finalized and in a
> > > "frozen" state by the 13th of July at the latest.
> > >
> > > Some deprecations should be non-controversial, others a bit more.
> > > If a deprecation is really controversial, it might warrant its own dedicated RFC or
> > > be dropped altogether.
> >
> > Reminder that there is less than a single week for adding deprecations before the RFC
> > needs to be in a frozen state.
> > A few people have added new ones and some were sent directly to me which I just added.
> > I also reordered some of the deprecations to group them together in somewhat more logical
> > places.
> >
> > https://wiki.php.net/rfc/deprecations_php_8_6
> >
> > If anyone has any issues or additional proposals they can still be added or amended.
> > If none are added or amended, I will initiate a call to vote next week.
>
> The RFC is now *frozen* no new proposals will be accepted.
> As some were added during the past week minimum of 2 weeks discussion is necessary.
> Amendments to existing proposals can be made ONLY IF they are minor changes according to the
> policy.
> I will initiate a call to vote next week on Monday (the 20th) for the following Monday (the
> 27th) so that the vote is done by the 10th of August.
> This should hopefully mean that most accepted proposals can land with 8.6..0beta1.
As said last week, I intend to open the vote next Monday (the 27th of July) for 2 weeks so that the
vote is finished on time for 8.6.
Best regards,
Gina P. Banyard