Re: [PHP-DEV] Re: [PHP-DEV] R e: [PHP-DEV] [RFC] [DISCUSSIO N] ext/gd 2.4 — codec sync, G d\* OOP API, 2D vector/canvas

On 20 July 2026 10:59:19 BST, Matteo Beccati <php@beccati=2Ecom> wrote:
>As much as I like this RFC, I'm afraid it came in a little too late=2E
>
>According to our reminders:
>
>> Any RFC intended for inclusion in PHP 8=2E6 must have its discussion co=
ncluded and its voting closed before August 13
>
>which isn't technically possible for this RFC if the voting period has to=
 be two weeks, even if no major discussion or modification happens=2E
>
>Unless my calculations are off, of course=2E


Just to confirm this with reference to policy:=20

- https://github=2Ecom/php/policies/blob/main/release-process=2Erst lists =
feature freeze as "$rd + 40", and states that all RFCs must be approved by =
that date
- https://github=2Ecom/php/policies/blob/main/feature-proposals=2Erst requ=
ires a minimum 14 day "cooldown period" from the initial announcement, and =
then a minimum 14 day voting period=20
- so cut-off is for an RFC to be in its final state by "$rd + 12" (40 - 14=
 - 14)

$rd is release date of first alpha, which was on July 2nd, so $rd+12 was J=
uly 14th=2E

Any RFC which was announced, or received a "major change", after that date=
, no longer has time to be approved before feature freeze=2E=20

Perhaps this milestone should be added explicitly to the "todo" wiki page =
in future=2E

(The release policy actually has an ambiguity: it says alpha1 should be ta=
gged on "first Tuesday in July", but released "before first Thursday in Jul=
y"=2E This year, the first Thursday came *before* the first Tuesday, so it =
was impossible to follow both requirements=2E The RMs apparently took the T=
hursday as the important deadline, and the tag was created on Tue June 30th=
, "$rd-2", which seems reasonable=2E I'll raise a PR if nobody else gets th=
ere first=2E)

Regards,

Rowan Tommins
[IMSoP]