Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:121653
Date: Fri, 10 Nov 2023 23:27:35 +0000
To: internals@lists.php.net
User-Agent: K-9 Mail for Android
In-Reply-To: <CAEKnhAHs-8aQwy89=xwgiLZzn=d8DKid9-S4m95jkNzxO0hARQ@mail.gmail.com>
References: <CAEKnhAHs-8aQwy89=xwgiLZzn=d8DKid9-S4m95jkNzxO0hARQ@mail.gmail.com>
Message-ID: <C00EF875-3749-4D16-B98B-941EF63DC436@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] [RFC] [Discussion] Release cycle update
From: rowan.collins@gmail.com (Rowan Tommins)

On 10 November 2023 16:51:57 GMT, Jakub Zelenka <bukka@php=2Enet> wrote:
>Hello,
>
>I would like to propose a new process RFC for updates to PHP release cycl=
e:
>
>https://wiki=2Ephp=2Enet/rfc/release_cycle_update

Hi,

I started writing a suggestion that you add details to your RFC of what te=
xt 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 d=
iff to go with it=2E

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"=2E I=
t also has parts that are obviously outdated ("Features can use branch(es) =
if necessary" - because the project was using SVN, where branches are costl=
y to maintain), parts in the future tense, and even open questions (about w=
ho can vote for RMs)=2E

So maybe what's really needed is to draft a new copy of the policy documen=
t, 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 R=
FC could contain proposed edits to that?

Regards,

--=20
Rowan Tommins
[IMSoP]