Several documents need to be updated as part of the release process. While the articles can be drafted in advance, they will only be published after the official announcement has been made.
Refer to the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. handbook for the complete overview of the major version release process. All the items that need updating can be found in the ‘Tell the World‘ and ‘Post Release’ sections.
These tasks are the responsibility of the Release Documentation Lead(s). Assistance can be requested from the documentation team in the Slack #docs channel.
Tell the World
HelpHub Release
The first item is the HelpHub Release or Version page under WP Versions.
A new version page is created by duplicating the previous version article—for example, Version 6.8. Specific items will need to be updated, and the release team will provide the necessary information. Refer to the notes on each item for guidance.
- Add the name of the jazzer. The name will be given to the release leadRelease Lead The community member ultimately responsible for the Release. on release-day.
- Update the link to the official announcement.
| On April 15, 2025, WordPress 6.8 “Cecil” was released to the public. For more information on this release, read the WordPress 6.8 announcement. |
- Update the db_version and the TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. revision. Ask in the SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. release team channel for the numbers.
For Version 6.8, the database version (db_version in wp_options) was 58975 and Trac revision was 60168. |
- Update the link to the full list of tickets included in the release.
| A full list of tickets included in 6.8 can be found on Trac. |
- The Installation/Update Information doesn’t update.
- The performance improvements link can be updated as soon as the post is live, usually the next day.
- On the Learn more about WordPress 6.x section, update the links to the field guide and the feature showcase. Change the release number at the end of the sentence.
| Explore the WordPress 6.8 Field Guide. Learn about the changes in this release with detailed developer notes to help you build with WordPress.Read the WordPress 6.8 Release Notes for information on installation, enhancements, fixed issues, release contributors, learning resources, and the list of file changes. Review the list of performance improvements.Visit the feature showcase for a full overview of all the new features and enhancements in WordPress 6.8. |
- Add the release squad from the WordPress 6.x Development Cycle post and update the release version number.
| Every release comes to you from a dedicated team of enthusiastic contributors who help keep things on track and moving smoothly. The team that has led 6.8 is a cross-functional group of contributors who are always ready to champion ideas, remove blockers, and resolve issues. |
- Update the changelog. This is done the day of the release and the Triage Lead or the Tech Lead usually has the list of files that go in the changelog. These can be added at a later date.
Updated packages@wordpress/a11y – 4.19.1 .. |
| List of files revised Modified files: license.txt |
WordPress Versions
The next document to update is the WordPress Versions page. For a major version, a new table blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. is added with the same columns and add the information:
- Version 6.x links to the minisite.
- Release date – add the date of the release.
- Musician – enter the name given to the release, not the jazzer full name.
- Changelog links to the HelpHub Release/Version release page.
- Announcement links to the formal release announcement.
- DB version – enter the db_version added in the HelpHub Release/Version release page.
- Update the changelog at the bottom.
- The Planned Versions section is also updated with any information available.
Post Release
Roadmap
Update the Roadmap by removing the latest release from the list of upcoming releases and fix the dates of any planned releases if the dates are known.
History
Update the History page by adding a new row to the table. Add the version number – it links to the official release announcement, add the jazzer (full name), and the release date.
These two pages must be updated simultaneously, as they will be pushed to the sandbox together to maintain version control. For more details, see Updating content on WordPress.org.
Learn about WordPress origins and version history
Update the article Learn about WordPress origins and version history:
- Add the year if it is the first release of the year. If it is not the first, add the version number next to the announcement
- Link the version number to the formal release announcement
- Begin the paragraph with the version number and name linked to version page
- Add the number of contributors
- Copy/paste the first paragraph from the release announcement.
- Add a link to the jazzer’s wikipedia page
| 2025 – Announcement: 6.8Version 6.8 (Cecil): (>900 contributors) Each WordPress release celebrates an artist who has left an indelible mark on music. WordPress 6.8, code-named “Cecil,” honors the legendary pianist and jazz pioneer Cecil Taylor. |
