Discussion: When to create the new branch

During both WP5.8 betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. packaging parties, the question was raised of when to create the new WP5.9 branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch".. Traditionally, this has been done when the release cycle reaches the first Release Candidaterelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). (RCrelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta).), but since we are trying out a different release cycle in WP5.8 it seems possible we could branch earlier.

Here are the discussions that have happened so far.

1. Original Discussion
2. Beta 1 Discussion
3. Beta 2 Discussion

The immediate scope of the discussion is: “Should we branch at beta 3 on 22 June, 2021 or should we continue the tradition of branching at RC1?”

I would appreciate us continuing this discussion here so that “being in the room” isn’t required. 🙂

#5-8