Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:115796
MIME-Version: 1.0
References: <CADK1yXLZzoOjjNcpZ5ZtV9kSNgw4=SW9G74o26eLdAYV5cDzAQ@mail.gmail.com>
 <alpine.DEB.2.23.453.2108241825130.2773@singlemalt.home.derickrethans.nl>
 <CADK1yXL=HdA5jF9F09vAgvZYzDpxcuN-1vxudwmZ6BXkjtuPKg@mail.gmail.com> <C7EF7C8B-A617-4C44-AAD5-B970098EC5AB@php.net>
In-Reply-To: <C7EF7C8B-A617-4C44-AAD5-B970098EC5AB@php.net>
Date: Tue, 24 Aug 2021 21:29:55 +0200
Message-ID: <CADK1yXLuSkMmfBumC4y9g4oP5dP06jgcLeh6S8K57Lum_3i8wQ@mail.gmail.com>
To: Derick Rethans <derick@php.net>, Tobias Nyholm <tobias.nyholm@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000b2c2dd05ca532a58"
Subject: Re: [PHP-DEV] Guidelines for RFC post feature-freeze
From: deleugyn@gmail.com (Deleu)

--000000000000b2c2dd05ca532a58
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Derick,

On Tue, Aug 24, 2021 at 9:09 PM Derick Rethans <derick@php.net> wrote:

> That's where I disagree already. The nullable intersections RFC isn't a
> refinement, it's a new feature.
>

And if I had voting powers, that would be exactly my reasoning for voting
no: "Not a Refinement RFC". However, whether a Refinement RFC can be
proposed or not is up to the Release Manager of the targeting version,
which is something that is included in the RFC to formalize what already
has precedence.

---------------------------------------------

Tobias,

On Tue, Aug 24, 2021, 21:00 Tobias Nyholm <tobias.nyholm@gmail.com> wrote:

>
> The issue I have with adding more guidelines for RFCs =E2=80=9Cpost featu=
re
> freeze=E2=80=9D is that it removes decision power from the release manage=
rs. Ie,
> one way of reading this proposal is that we don=E2=80=99t trust the relea=
se
> managers to decide what to include and not to include in a release.


I'm interested in understanding how the proposal gives this impression
because others may end up in a similar conclusion and that is far from the
intention. Is there a specific part of the text that makes it look like
release managers are being stripped of any power?

In my perspective, the only way of reading this RFC is:

- RFC Authors: don't be afraid of attempting a last-minute change. Just
talk to the Release Managers first as it will affect their work.
- Release Managers: if a code change looks like it needs an RFC and it will
clash with feature freeze, you have the power to provide a speedy RFC by
allowing a Refinement RFC.
- Voters: When voting on a Refinement RFC, be aware that it may move
slightly faster due to time sensitivity and judge for yourself the merits
of the proposal.


> To allow the release managers to have this decision power is not a
> =E2=80=9Cviolation of voter rights=E2=80=9D, that is just a silly argumen=
t.
>

Well, thank you?


> Maybe we should hear what the current and previous release managers think=
?
> Do they feel like they need more policies around their work?
>
> // Tobias


Gabriel Caruso, release manager of 8.0 has shown his support on this
discussion in the first reply of this thread.

--=20
Marco Aur=C3=A9lio Deleu

--000000000000b2c2dd05ca532a58--