rfc:release_cycle_update

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
rfc:release_cycle_update [2024/03/21 17:50] – Rewrite, reorder, and added end-of-cycle fixing to Dec 31st derickrfc:release_cycle_update [2024/04/09 10:41] (current) – derick
Line 3: Line 3:
   * Date: 2024-03-21   * Date: 2024-03-21
   * Authors: Jakub Zelenka <bukka@php.net>, Derick Rethans <derick@php.net>   * Authors: Jakub Zelenka <bukka@php.net>, Derick Rethans <derick@php.net>
-  * Status: Under Discussion+  * Status: Voting
  
 ===== Introduction ===== ===== Introduction =====
Line 12: Line 12:
 It is also quite risky to introduce more complex fixes later in the active support cycle as the security support does It is also quite risky to introduce more complex fixes later in the active support cycle as the security support does
 not allow fixing potential regressions. In addition, it is not exactly clear which features can be introduced during not allow fixing potential regressions. In addition, it is not exactly clear which features can be introduced during
-beta, RC, and bug fix releases. And the number of pre-releases seems unnecessarily long, especially during the RC stage +the beta period, Release Candidates, and Bug Fix releases. 
-where there are very few RC specific changes.+ 
 +The number of pre-releases also seems unnecessarily long, especially during the Release Candidate stage, 
 +where there are few Release Candidate specific changes.
  
 ===== Proposal ===== ===== Proposal =====
  
-This RFC aims to address above issues and proposes to introduce the following changes to the release cycle.+This RFC aims to address the above issues and proposes to introduce the following changes to the release cycle:
  
  
Line 132: Line 134:
 If any of the proposed changes passes, the [[https://github.com/php/policies/blob/main/release-process.rst|Release Process policy document]] If any of the proposed changes passes, the [[https://github.com/php/policies/blob/main/release-process.rst|Release Process policy document]]
 will be updated with any accepted changes, and currently operating rules. will be updated with any accepted changes, and currently operating rules.
 +
 +Voting runs until **Monday April 29th, at noon UTC**.
 +
 +<doodle title="Allow features that do not require an RFC in the beta period" auth="derick" voteType="single" closed="false" closeon="2024-04-29T12:00:00Z">
 +   * Yes
 +   * No
 +</doodle>
 +
 +
 +----
 +
 +
 +<doodle title="Disallow New Features in Release Candidates and Bug Fix releases" auth="derick" voteType="single" closed="false" closeon="2024-04-29T12:00:00Z">
 +   * Yes
 +   * No
 +</doodle>
 +
 +----
 +
 +
 +<doodle title="Reduce number of RCs to Four" auth="derick" voteType="single" closed="false" closeon="2024-04-29T12:00:00Z">
 +   * Yes
 +   * No
 +</doodle>
 +
 +----
 +
 +<doodle title="Extend Security Support by One Year" auth="derick" voteType="single" closed="false" closeon="2024-04-29T12:00:00Z">
 +   * Yes
 +   * No
 +</doodle>
 +
 +----
 +
 +<doodle title="Allowing recent regression fixes during security support" auth="derick" voteType="single" closed="false" closeon="2024-04-29T12:00:00Z">
 +   * Yes
 +   * No
 +</doodle>
 +
 +----
 +
 +<doodle title="Extend Releases Cycle to End of Year" auth="derick" voteType="single" closed="false" closeon="2024-04-29T12:00:00Z">
 +   * Yes
 +   * No
 +</doodle>
 +
 +
 +
  
  
rfc/release_cycle_update.1711043417.txt.gz · Last modified: 2024/03/21 17:50 by derick

Page Tools