Re: Guidelines for RFC post feature-freeze
| From: | Ben Ramsey | Date: | Wed, 25 Aug 2021 20:25:02 +0000 |
| Subject: | Re: Guidelines for RFC post feature-freeze | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-115834@lists.php.net to get a copy of this message | ||
Deleu wrote on 8/24/21 13:53:
> The proposal is rooted in making it easier for release managers and rfc
> authors to refine code changes that may or may not be necessary to
> accomplish a previously approved RFC.
I don't understand how this proposal helps with this. If changes are
necessary to accomplish a previously approved RFC, that means the RFC
isn't fully implemented, so there are bugs, and bugs should be addressed
using the normal bugfix process. They shouldn't require another RFC.
If a change requires another RFC, that means something is being proposed
that changes the behavior of a previous RFC (or adds to it). This is a
new feature.
Cheers,
Ben
Attachment: [application/pgp-signature] OpenPGP digital signature signature.asc
Attachment: [application/pgp-signature] OpenPGP digital signature signature.asc