Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:122713
Date: Thu, 21 Mar 2024 18:54:49 +0100 (CET)
To: PHP internals list <internals@lists.php.net>
cc: Jakub Zelenka <bukka@php.net>
Subject: [PHP-DEV] [RFC] Release cycle update, take #2
In-Reply-To: <CAEKnhAHs-8aQwy89=xwgiLZzn=d8DKid9-S4m95jkNzxO0hARQ@mail.gmail.com>
Message-ID: <04736cc6-0372-8228-7d2a-7e12453a8f0c@php.net>
References: <CAEKnhAHs-8aQwy89=xwgiLZzn=d8DKid9-S4m95jkNzxO0hARQ@mail.gmail.com>
Precedence: bulk
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="8323329-1419104960-1711043689=:29878"
From: derick@php.net (Derick Rethans)

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--8323329-1419104960-1711043689=:29878
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: QUOTED-PRINTABLE

Hi!

On Fri, 10 Nov 2023, Jakub Zelenka wrote:

> I would like to propose a new process RFC for updates to PHP release=20
> cycle:
>=20
> https://wiki.php.net/rfc/release_cycle_update

I have just published version 0.2 of this proposal =E2=80=94 I am taken thi=
s=20
over from Jakub by agreement.

I've slightly reordered it, addressed some comments from this thread,=20
and added one new item: aligning the end of releases until Dec 31st,=20
20xx.

Now that we have policy documents, my next step is to prepare PRs to=20
https://github.com/php/policies/blob/main/feature-proposals.rst for each=20
item, after a more general reset of the document to reflect current=20
practises.

The RFC is at https://wiki.php.net/rfc/release_cycle_update

cheers,
Derick
--8323329-1419104960-1711043689=:29878--