Hi Jakub Thank you for the proposal.
On Fri, Nov 10, 2023 at 5:52 PM Jakub Zelenka <bu...@php.net> 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 targeting > that version must have voting finished but the implementation can be done > during beta. This is however a major inconsistency because RFC > implementations are often those that can have a major impact on API and ABI > stability so it seems illogical to allow that but don't allow minor > improvements that do not require RFC. I think the general expectation with the current process is that an RFC implementation would be merged reasonably shortly after feature freeze. Extending this to the entire beta period may be risky, especially if we're also shortening the RC period. With an implementation merged last-minute, this gives us 2 months to iron out any issues. With multiple RFCs merged last-minute things could become quite overwhelming. I also think library maintainers might want more than 2 months time to make and test their changes, especially when it comes to BC incompatible changes. I'm not sure how this can be addressed. We should at least encourage changes to be merged early in the beta cycle. Ilija -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: https://www.php.net/unsub.php
