Hey Matteo :)
On Fri, Jul 31, 2026, 12:00 AM Matteo Beccati <[email protected]> wrote: > Hi Seifeddine, > > Il 30/07/2026 01:59, Seifeddine Gmati ha scritto: > > I asked the 8.6 Release Manager about the feature freeze. The > > effective cutoff is not the beta1 announcement on August 13 but the > > creation of the beta1 tag, which happens on Tuesday, August 11, > > mid-morning US Central time. A vote opened today would close on August > > 13, after the tag exists, so inclusion in 8.6 is not possible. I will > > therefore not reopen the vote, and the Intent to Vote I posted on July > > 23 is withdrawn. > > > > I have retargeted the RFC to the next PHP version, whether that is 8.7 > > or 9.0. RFC text is otherwise unchanged and remains final: > > https://wiki.php.net/rfc/literal_scalar_types > I could have made an honest mistake when announcing the deadlines, but > all my emails were pointing the 13th as deadline for RFCs. > > The rationale being that the implementation didn't have to land in beta1 > necessarily, so the beta1 release date seemed better than "tagging day" > as deadline. > > I think that having RFCs end voting so close to the feature freeze is a > terrible idea as it gives very little wiggle room in case something > unexpected comes out once implemented and more widely tested. > beta phases exist exactly for this reason. wider base of testers. alpha is, heh, this is what we have so far, more or less stable, go test it already! RCs are everything should be stable, that's the final state, last stage(s) for any bugs or breaks that didn't get caught earlier. we should not expect "widely tested" new features, never released before per se. between the limited time induced by the updated policies, the Christmas break "pls don't", and this, one needs to take holidays to make it somehow as the time left in a year is low, very low, now. That said, another RFC went to voting a few minutes ago, so we'd better > be consistent. I apologise for the confusion! > I can't talk for the author, you are in your role here :) applying policies, even broken ones :) -- Pierre @pierrejoye >
