Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:122807
Date: Fri, 29 Mar 2024 16:31:51 +0000 (GMT)
To: Jim Winstead <jimw@trainedmonkey.com>
cc: PHP internals list <internals@lists.php.net>, 
    Jakub Zelenka <bukka@php.net>
Subject: Re: [PHP-DEV] [RFC] Release cycle update, take #2
In-Reply-To: <45598d80-7834-4355-9b30-b5da99a611f4@app.fastmail.com>
Message-ID: <0f7c5be6-25ff-78ef-6212-1ef1f3982cf2@php.net>
References: <CAEKnhAHs-8aQwy89=xwgiLZzn=d8DKid9-S4m95jkNzxO0hARQ@mail.gmail.com> <04736cc6-0372-8228-7d2a-7e12453a8f0c@php.net> <45598d80-7834-4355-9b30-b5da99a611f4@app.fastmail.com>
Precedence: bulk
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="8323329-29361424-1711729911=:14553"
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-29361424-1711729911=:14553
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: QUOTED-PRINTABLE

On Thu, 21 Mar 2024, Jim Winstead wrote:

> On Thu, Mar 21, 2024, at 10:54 AM, Derick Rethans wrote:
> > 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=
 this=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 eac=
h=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
>=20
> Could this RFC also be a good time to clarify what sort of BC changes=20
> are actually allowed in major and minor releases, or should we save=20
> that for a different RFC? (Because it's already been acknowledged that=20
> the current written policy doesn't align with the practiced policy,=20
> and I think it would be nice to get those in sync.)

I'm planning in doing a rewrite of the whole policy document on releases=20
(https://github.com/php/policies/blob/main/release-process.rst) and then=20
RFCing the changes. That document also contains as to what a bug fix is.

cheers,
Derick

--=20
https://derickrethans.nl | https://xdebug.org | https://dram.io

Author of Xdebug. Like it? Consider supporting me: https://xdebug.org/suppo=
rt

mastodon: @derickr@phpc.social @xdebug@phpc.social
--8323329-29361424-1711729911=:14553--