Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:121651
Message-ID: <49b2333b-c8c1-4fad-89ed-db559108d779@bastelstu.be>
Date: Fri, 10 Nov 2023 22:01:56 +0100
MIME-Version: 1.0
Content-Language: en-US
To: Jakub Zelenka <bukka@php.net>, Ilija Tovilo <tovilo.ilija@gmail.com>
Cc: PHP internals list <internals@lists.php.net>
References: <CAEKnhAHs-8aQwy89=xwgiLZzn=d8DKid9-S4m95jkNzxO0hARQ@mail.gmail.com>
 <CAPyj-LA278v4mEL3+BmxUUBgk5dW6x=Dssy-4RwWzAe0X4mqqQ@mail.gmail.com>
 <CAEKnhAGShvTi3UPqvw07Kkf2VP8c4YgNJ9Pj9GUR2QbUVhqrag@mail.gmail.com>
In-Reply-To: <CAEKnhAGShvTi3UPqvw07Kkf2VP8c4YgNJ9Pj9GUR2QbUVhqrag@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] [RFC] [Discussion] Release cycle update
From: tim@bastelstu.be (=?UTF-8?Q?Tim_D=C3=BCsterhus?=)

Hi

On 11/10/23 21:22, Jakub Zelenka wrote:
> - 2 alphas - think 2 are enough as each RM can try one release.
> - 4 betas and require that all RFC has to be merged before beta3 is
> released. It means we would have 2 extra betas to iron out all RFC issues
> and still be able to introduce ABI breaks

Should this read: "before beta 3 is tagged"? An RFC could be merged 
after the tag and before the release, and then there would only one 
remaining Beta for it.

> - 4 RC - real feature freeze without any ABI or API breaks

Best regards
Tim Düsterhus