Re: [RFC] Release cycle update, take #2
| From: | Morgan | Date: | Thu, 21 Mar 2024 20:34:18 +0000 |
| Subject: | Re: [RFC] Release cycle update, take #2 | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-122717@lists.php.net to get a copy of this message | ||
On 2024-03-22 08:19, Jim Winstead wrote:
On Thu, Mar 21, 2024, at 10:54 AM, Derick Rethans wrote:The RFC is at https://wiki.php.net/rfc/release_cycle_updateCould this RFC also be a good time to clarify what sort of BC changes are actually allowed in major and minor releases, or should we save that for a different RFC? (Because it's already been acknowledged that the current written policy doesn't align with the practiced policy, and I think it would be nice to get those in sync.) If so, would it also good time/place to clarify how deprecation relates to future removal. Say, while deprecations could come in any minor release, they would be removed only after a full major version has elapsed (something deprecated in 8.x would be removed in 10.0; technically that would mean a deprecation in 9.0.0 would also mean removal in 10.0). It would allow using the overall release cycle to forecast when something you're currently relying on will go away and plan accordingly.