The WordPress coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:
Found a bugbugA bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority.?Create a ticket in the bug tracker.
Update 7 NOV 2022: Added @mamaduka as the Release Editor Tech Lead.
Update 9 NOV 2022: Added Bug Scrub for Thurs, Nov 10th.
Coming after the WordPress 6.1 release earlier this week, both @desrosj and I are planning to lead a 6.1.1 release for some fast-follow items that came up near the end of the 6.1 release cycle and have bubbled up post-release such that we would like to try and ship before the end-of-year holidays start to pull folks away from contributing. If there is a critical bugfix that has a patchpatchA 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./PR ready, then please look to add those to the 6.1.1 milestone in Trac or the WordPress 6.1.1 Editor Tasks project board in GitHub.
The following schedule is what’s currently planned for the release, any additional bugbugA bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. scrubs, release candidates, or other items will be added here as they get scheduled.
Bug Scrub focused on finalizing items for 6.1.1 in TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress./GitHubGitHubGitHub is a website that offers online implementation of git repositories that 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/ (Slack archive)
Bug Scrub ahead of RCrelease candidateOne 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). (Slack archive)
Given the short timeline planned for this release, we are leveraging folks from the 6.1 release squad to help get 6.1.1 released in an expeditious manner. All others are welcome to help during bug scrubs, working on patches/PRs, testing patches/PRs, and participating in any release parties.
ReleaseCoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Tech Lead:@desrosj
Release Editor Tech Lead:@mamadukaTBD (if you’re interested and available, please reach out to @jeffpaul or @desrosj or comment on this post, thanks!)
The #6-1-release-leads channel will continue to be used for all coordination and conversation related to the 6.1.x releases. This matches the pattern of communication that worked well for previous minor releaseMinor ReleaseA set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality. cycles!
Additional 6.1.x Releases
The 6.1.1 release is the final release planned for 2022, a 6.1.2 seems feasible around the end of January but the Core team will want to look to confirm formal 6.1.x Minor Release Leads by then who can help shepherd future minor releases on the 6.1 branchbranchA 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". (cc: @audrasjb@marybaum).