The 6.0.x releases will follow the same consistent minor release leads strategy as the 5.8.x releases and 5.9.x releases did. For the 6.0.1 point releases, the release leads will be:
- Release Lead The community member ultimately responsible for the Release. / Core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. tech: @sergeybiryukov
- Release Deputy / Editor tech: @zieladam
@zieladam is going to help with 6.0.1 but, for a 6.0.2, there’s an opening if someone is able to help. I’ll keep this post up to date as that changes.
6.0.1 proposed schedule
The following schedule is being proposed for 6.0.1:
- Release 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).: July 5th, 2022
- Final release: July 12, 2022
@sergeybiryukov will run mission control for this release.
Trac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets update
As of the publish date of this post, 4 Trac Tickets have been fixed and are ready to be backported to the 6.0 branch 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". to be included in 6.0.1. 6 additional tickets either need testing or have a patch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. in order to be considered for backporting.
GitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ issues updates
As of the publish date of this post, there are 13 pull requests ready for backporting to the 6.0 branch.
The #6-0-release-leads channel will continue to be used for all coordination and conversation related to the 6.0.x releases. This matches the pattern of communication that worked well for the 5.9.x cycle!