Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:115783
MIME-Version: 1.0
References: <CADK1yXLZzoOjjNcpZ5ZtV9kSNgw4=SW9G74o26eLdAYV5cDzAQ@mail.gmail.com>
 <CF38091C-FE8E-4234-970A-4A16B1046EA4@gmail.com>
In-Reply-To: <CF38091C-FE8E-4234-970A-4A16B1046EA4@gmail.com>
Date: Tue, 24 Aug 2021 08:13:45 +0530
Message-ID: <CAMkukMxuGJm-dKCMVCpVT7R8h5_DjECi=cDctFKYX8jTdceP_g@mail.gmail.com>
To: Tobias Nyholm <tobias.nyholm@gmail.com>
Cc: Deleu <deleugyn@gmail.com>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000f3b82405ca451a36"
Subject: Re: [PHP-DEV] Guidelines for RFC post feature-freeze
From: faizanakram99@gmail.com (Faizan Akram Dar)

--000000000000f3b82405ca451a36
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Tue, 24 Aug 2021, 4:27 am Tobias Nyholm, <tobias.nyholm@gmail.com> wrote=
:

> Thank you.
> I appriciate you bring up this issue.
>
> Situations like this often requires a judgement call rather than somethin=
g
> that could be defined as a policy.
> I suggest the release managers always should be in agreement before a RFC
> is created during a =E2=80=9Cfeature freeze=E2=80=9D. If the release mana=
gers agree that a
> change can be added, then the discussion and the vote should not consider
> =E2=80=9Cif it is too late=E2=80=9D or =E2=80=9Cthis is rushed=E2=80=9D. =
I think we can trust the release
> managers to make the correct desiccation without an extra policy.
>
> // Tobias
>
> > On 23 Aug 2021, at 13:48, Deleu <deleugyn@gmail.com> wrote:
> >
> > Hello everyone!
> >
> > We recently had the Nullable Intersection Types RFC process in an
> > unconventional way starting a new RFC post feature freeze. If memory
> serves
> > me right, another similar incident happened with the Attributes RFC whi=
ch
> > had a syntax that could not be implemented without a secondary RFC [1]
> and
> > went through a secondary RFC which proposed a different syntax [2].
> >
> > [1] https://wiki.php.net/rfc/namespaced_names_as_token
> > [2] https://wiki.php.net/rfc/attributes_v2
> >
> > I would like to gather opinion on a potential Policy RFC that would
> define
> > some guidelines for such a process. As Nikita pointed out [3], the
> ability
> > to refine new features is both important for the developer and
> undocumented
> > for the PHP Project.
> >
> > In order to not be empty-handed, I started a gist that can be seen as t=
he
> > starting point for this discussion, available at
> > https://gist.github.com/deleugpn/9d0e285f13f0b4fdcfc1d650b20c3105.
> >
> > Generally speaking, I'm first looking for feedback on whether this is
> > something that deserves attention and an RFC or is it so rare that it's
> > fine to leave it unchanged. If there is interest in moving forward, I
> would
> > then also be interested in suggestions on things that should be
> > included/excluded in the RFC.
> >
> > Marco Aur=C3=A9lio Deleu
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: https://www.php.net/unsub.php


Hi,

I agree with Tobias. Such changes / requests are rare and require a
judgement call.

PS: Sorry if my email was posted twice, I replied via a different email
which is not subscribed to internals list, so wasn't sure.

--000000000000f3b82405ca451a36--