Re: [RFC] [Discussion] Release cycle update
| From: | Derick Rethans | Date: | Mon, 13 Nov 2023 14:33:22 +0000 |
| Subject: | Re: [RFC] [Discussion] Release cycle update | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-121665@lists.php.net to get a copy of this message | ||
On 10 November 2023 23:27:35 GMT, Rowan Tommins <rowan.collins@gmail.com> wrote:
>On 10 November 2023 16:51:57 GMT, Jakub Zelenka <bukka@php.net> wrote:
>>Hello,
>>
>>I would like to propose a new process RFC for updates to PHP release cycle:
>>
>>https://wiki.php.net/rfc/release_cycle_update
>
>Hi,
>
>I started writing a suggestion that you add details to your RFC of what text we would remove or
>change in the existing policy if approved - what you've presented so far is like a good commit
>message, but we probably want a diff to go with it.
>
>However, looking at the existing "policy", most of the things you want to change
>aren't actually in it - it doesn't even contain the word "beta". It also has
>parts that are obviously outdated ("Features can use branch(es) if necessary" - because
>the project was using SVN, where branches are costly to maintain), parts in the future tense, and
>even open questions (about who can vote for RMs).
>
>So maybe what's really needed is to draft a new copy of the policy document, updating or
>removing those parts that are no longer relevant, and adding a timeline for the pre-release phases?
>
>Or possibly there's a different document I should be looking at, and the RFC could contain
>proposed edits to that?
>
>Regards,
>
I already have been collecting most of the policy things together in one document:
https://docs.google.com/document/d/1Wc84ZxHHamvWsZl-U2kFOrbJDEXyXFv1laePN4ijJGQ/edit?usp=drivesdk
For the same reasons really. The info was spread out a lot.
cheers
Derick