Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:115844
MIME-Version: 1.0
References: <CADK1yXLZzoOjjNcpZ5ZtV9kSNgw4=SW9G74o26eLdAYV5cDzAQ@mail.gmail.com>
 <CAEZPtU5STkockXmwYBQi0kd+rBtNkb9Z4UwvxMe7ozRSDTm8Ew@mail.gmail.com>
 <CAOWwgpmEpzPURtcASMH_VLNdtb0Qmhg5HEOuRFRZ4x+97KteLw@mail.gmail.com>
 <CADyq6sLBpywgXdFqGYFuKek4FHzOZpvARZa3mS_ovoDmBxbOWw@mail.gmail.com>
 <CAOWwgpnZ=vtwqD8zGDSKFNpC0Gs1VScayVXQ3GyM5-S2DmPu5g@mail.gmail.com> <B096EE9F-35EC-42A1-8196-F25415A373D1@php.net>
In-Reply-To: <B096EE9F-35EC-42A1-8196-F25415A373D1@php.net>
Date: Thu, 26 Aug 2021 10:19:06 +0700
Message-ID: <CAEZPtU4H0cXv9H9QyBCymHdc_46B93UfiHzHOAd-oOY4fZGGcw@mail.gmail.com>
To: Derick Rethans <derick@php.net>
Cc: PHP internals <internals@lists.php.net>, Nicolas Grekas <nicolas.grekas+php@gmail.com>, 
	Marco Pivetta <ocramius@gmail.com>, Deleu <deleugyn@gmail.com>
Content-Type: multipart/alternative; boundary="0000000000000e648105ca6dd519"
Subject: Re: [PHP-DEV] Guidelines for RFC post feature-freeze
From: pierre.php@gmail.com (Pierre Joye)

--0000000000000e648105ca6dd519
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi,

On Thu, Aug 26, 2021, 1:09 AM Derick Rethans <derick@php.net> wrote:

> On 25 August 2021 18:34:18 BST, Nicolas Grekas <
> nicolas.grekas+php@gmail.com> wrote:
> >Le mer. 25 ao=C3=BBt 2021 =C3=A0 19:32, Marco Pivetta <ocramius@gmail.co=
m> a =C3=A9crit
> :
> ,
> >
> >> On Wed, Aug 25, 2021 at 7:30 PM Nicolas Grekas <
> >> nicolas.grekas+php@gmail.com> wrote:
> >>
> >>> I would welcome a new RFC to clarify what is allowed during the featu=
re
> >>> 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 softwar=
e
> development is some time were no new features are added so a code base ca=
n
> 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 perio=
d
> can also be used by users to make sure everything is stable, and that the=
re
> 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

>

--0000000000000e648105ca6dd519--