Hi, On Thu, Aug 26, 2021, 1:09 AM Derick Rethans <der...@php.net> wrote:
> On 25 August 2021 18:34:18 BST, Nicolas Grekas < > nicolas.grekas+...@gmail.com> wrote: > >Le mer. 25 août 2021 à 19:32, Marco Pivetta <ocram...@gmail.com> a écrit > : > , > > > >> On Wed, Aug 25, 2021 at 7:30 PM Nicolas Grekas < > >> nicolas.grekas+...@gmail.com> wrote: > >> > >>> I would welcome a new RFC to clarify what is allowed during the feature > >>> freeze. > >>> > >> > >> See https://en.wikipedia.org/wiki/Freeze_(software_engineering) > >> > > > > > >Can you please let me know how that helps? > > Maybe you didn't read the post, but generally a feature freeze in software > development is some time were no new features are added so a code base can > stabilise. This usually happens just before a release. These periods are > really important as they allow for 3rd party tools, documentation, etc to > be ready when a piece of software is released. On top of that, this period > can also be used by users to make sure everything is stable, and that there > are no critical bugs. > I suppose everyone knows what a freeze is. Also the issue here is not about the PHP features freeze period (RMs do a good job here to announce and update it well on advance). It is about amending RFC for completeness (or whatever other reasons). I can understand a RFC author does not want it for some random extension being added. However I do see challenges when it comes to the very PHP core syntax and languages. As we expected many years ago when we introduced the RFC process, I do see a need to slightly clarify how the core of the PHP language is handled. Not to block any changez but really to make it clear, what we can accept, veto possible (it is now), etc. For the discussion about whether the null intersection was a feature or a refinement, I would suggest just to ignore it. too late too little. best, Pierre >
