On 10-11-2023 17:51, Jakub Zelenka 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
This has been discussed between release managers to make sure that all are
happy as some of the points impact release manag
On 10 November 2023 23:27:35 GMT, Rowan Tommins wrote:
>On 10 November 2023 16:51:57 GMT, Jakub Zelenka 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
On 10 November 2023 20:22:27 GMT, Jakub Zelenka wrote:
>Hi,
>
>On Fri, Nov 10, 2023 at 5:56 PM Ilija Tovilo wrote:
>
>I think there should be a clear cut when the RFC can be implemented and
>there should be probably still time to apply ABI breaking changes after
>that time. So we could potentiall
Le 10/11/2023 à 17:51, Jakub Zelenka a écrit :
Hello,
I would like to propose a new process RFC for updates to PHP release cycle:
https://wiki.php.net/rfc/release_cycle_update
> Extending security support by one year
+1
> Allowing recent regression fixes during security support
As regress
2023年11月11日(土) 8:27 Rowan Tommins :
>
> On 10 November 2023 16:51:57 GMT, Jakub Zelenka 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
On 10 November 2023 16:51:57 GMT, Jakub Zelenka 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 chan
On Fri, Nov 10, 2023, at 2:11 PM, Jakub Zelenka wrote:
> Hi,
>
> On Fri, Nov 10, 2023 at 5:20 PM Larry Garfield
> wrote:
>
>>
>> * "Allow feature that do not require RFC in beta" - The description
>> doesn't quite sound like it's talking about "features." It's talking about
>> refactoring, bug f
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
Sho
Hi,
On Fri, Nov 10, 2023 at 5:56 PM Ilija Tovilo wrote:
> Hi Jakub
>
> Thank you for the proposal.
>
> On Fri, Nov 10, 2023 at 5:52 PM Jakub Zelenka wrote:
> > https://wiki.php.net/rfc/release_cycle_update
>
> > Currently beta is called a feature freeze but effectively it isn't. The
> main issu
Hi,
On Fri, Nov 10, 2023 at 5:20 PM Larry Garfield
wrote:
>
> * "Allow feature that do not require RFC in beta" - The description
> doesn't quite sound like it's talking about "features." It's talking about
> refactoring, bug fixes, edge case handling, etc. Those are certainly
> beta-friendly
Hi Jakub
Thank you for the proposal.
On Fri, Nov 10, 2023 at 5:52 PM Jakub Zelenka wrote:
> https://wiki.php.net/rfc/release_cycle_update
> Currently beta is called a feature freeze but effectively it isn't. The main
> issue with that is that the end of alpha just means that all RFC's targetin
On Fri, Nov 10, 2023, at 10:51 AM, Jakub Zelenka 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
>
> This has been discussed between release managers to make sure that all are
> happy as some of the po
Hello,
I would like to propose a new process RFC for updates to PHP release cycle:
https://wiki.php.net/rfc/release_cycle_update
This has been discussed between release managers to make sure that all are
happy as some of the points impact release managers (e.g. longer security
support).
I also
13 matches
Mail list logo
