Re: [RFC] php-community: a faster-moving, community-driven PHP.
| From: | Daniil Gentili | Date: | Mon, 16 Mar 2026 17:24:11 +0000 |
| Subject: | Re: [RFC] php-community: a faster-moving, community-driven PHP. | ||
| References: | 1 2 3 4 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-130368@lists.php.net to get a copy of this message | ||
Version 1.1.0 of the RFC was published:
#### 1.1.0
- **Voting (clarification)** — Clarified that only internals members with voting rights count for
quorum/veto calculations, and emphasized internals-only quorum wording.
- **Community RFC owners (clarification)** — Clarified that compatibility fixes caused by breaking
internal PHP API changes are handled by whoever introduces those breaking changes.
- **Removal of community RFC features (policy update)**
Removal voting remains open to all for sentiment, but only internals votes are counted for outcome.
Eligibility changed from strict
AND conditions to an OR policy:
- no active owners (defined as no commits and no replies from listed owners in 6 months; with owner
removal possible in case of violations);
- or negligible adoption, based on Packagist stats/telemetry.
Deprecation period after acceptance of a removal RFC was reduced from at least 3 stable
php-community releases to at least 1 stable release.
- **Feature extensions (new clarifications)** — Added guidance that releases should ideally ship
all major versions of feature extensions together, that security updates apply to all currently
shipped versions, and that retiring old majors is up to feature owners based on adoption.