Dev Chat Agendas | Dev Chat Summaries | Bug Scrubs Schedule | Dev Notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. | Field GuideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page. | All Posts Tagged 6.2

WordPress 6.2 will be the fist major release of 2023 and is in the early planning stages. Check back in as more information is made available.

Release team

  • Release LeadRelease Lead The community member ultimately responsible for the Release.:
  • Release Coordinators: 
  • CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Tech Co-Leads:
  • Editor Tech Co-Leads: 
  • Core Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. Co-Leads:
  • Editor Triage Lead: 
  • Documentation Co-Leads: 
  • Marketing & Communications Co-Leads: 
  • Test Lead: 
  • Design Lead: 

All release decisions will ultimately be this release teams’ to make and communicate while gathering input from the community.

Release Schedule

10/18/2022Alpha Begins. Trunk is open for business.
TBD. 6.2 Pre-planning post.
Early ticketticket Created for both bug reports and feature development on the bug tracker. freeze. Any early tickets not yet committed will be moved to the 6.3 or Future Release milestones.
Walkthrough. A live and moderated review of features slated for the release.
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. 1. From this point on, core contributorsCore Contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. will focus on testing and fixing bugs discovered during beta testing. Begin writing Dev Notes and the About page (SlackSlack Slack is a Collaborative Group Chat Platform The WordPress community has its own Slack Channel at archive, ZIP download).
Beta 2. Test the beta release, fix bugs discovered during beta testing, and continue writing Dev Notes and the About page (Slack archive, ZIP download).
Beta 3. Test the beta release, fix bugs discovered during beta testing, continue writing Dev Notes and the About page, and soft string freeze (Slack archive, ZIP download).
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). 1. Publish the Field Guide with Dev Notes, commit the About page, begin drafting the release post, hard string freeze, and 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". for the release. (Slack archive, ZIP download).
Release candidate 2. Update the About page images and continue drafting the release post (Slack archive, ZIP download).
Release candidate 3. Update the About page images and continue drafting the release post (Slack archive, ZIP download).
Dry run for release of WordPress 6.2 and 24-hour code freeze (Slack archive).
TBD. WordPress 6.2 is released (Slack archive, ZIP download)!

How to contribute

To get involved in WordPress core development, head over to TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress., and pick a 6.2 ticket. Need help? Check out the Core Contributor Handbook.

Get your patches done and submitted as soon as possible, then help find people to test the patches and leave feedback on the ticket. Patches for enhancements will not be committed after the dates posted above so that we can all focus on squashing bugs and deliver the most bugbug A 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.-free WordPress ever 😉

If you want to dive deeper into 6.2, join the weekly meetings in the #core Slack channel, which occur next at Wednesday at 20:00 UTC, and the editor-focused meetings in the #core-editor Slack channel, every Wednesday at 14:00 UTC