WordPress 6.7 Planning Proposal & Call for Volunteers

  • Please leave your feedback about the schedule and release squad size in the comments by July 19th.
  • If you are interested in participating in WordPress 6.7’s release squad as a lead, please show interest in the comments below, clearly specifying the role.

With WordPress 6.6 almost ready, it’s time to start planning WordPress 6.7 so that the release leads can participate from the start of the release cycle.

The timeline for the third release of 2024 takes into consideration WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. US in mid-September. To avoid having major milestones (Beta1, RC1) conflictconflict A conflict occurs when a patch changes code that was modified after the patch was created. These patches are considered stale, and will require a refresh of the changes before it can be applied, or the conflicts will need to be resolved. with flagship events, this proposal suggests having WordPress 6.7 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 after WordCamp US with a small buffer in between.

According to the schedule proposed below and the GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ release cadence, WordPress 6.7 would include up to Gutenberg 19.3 for a total of 8 Gutenberg releases.

Proposed WordPress 6.7 Schedule

MilestoneDate
Alpha (trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision. open for 6.7 release)June 25, 2024
Last Gutenberg 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). before Beta 1September 18, 2024
Beta 1October 1, 2024
Beta 2October 8, 2024
Beta 3October 15, 2024
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). 1October 22, 2024
Release Candidate 2October 29, 2024
Release Candidate 3November 5, 2024
Dry RunNovember 11, 2024
WordPress 6.7 General ReleaseNovember 12, 2024

Please leave your feedback about the schedule in the comments by July 19th.

Release Leads call for volunteers

With the recent switch to using the microsite as the base for the About page, some of the Marcomms lead’s responsibilities increasingly overlap with the Design Lead. Considering recurring feedback about the excessive number of release roles, we propose experimenting with combining the Marcomms and Release Coordination roles. This new consolidated role would absorb the duties of the Marcomms lead, streamline communication, and enhance collaboration, addressing the feedback on role complexity and redundancy while improving overall efficiency.

Leads in the squad should have proven experience and availability during the release cycle. Less experienced folks and newcomers are still welcome to follow along the process in preparation for future releases.

Some roles have already been filled by volunteers from the previous call, while others remain open. The TBDs in the list below indicate the number of spots that still need to be filled.

  • Release LeadRelease Lead The community member ultimately responsible for the Release.: Matt Mullenweg
  • Release Coordination and Communications: TBD
  • CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Tech Leads: Peter Wilson, Kira Schroder
  • Editor Tech Leads: Robert Anderson, Kai Hao
  • Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. Leads: TBD
  • Documentation Leads: TBD
  • Test Lead: TBD
  • Design Lead: TBD
  • Performance Lead: TBD
  • Default Themes Lead: TBD

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

As a reminder, if you are interested in participating in WordPress 6.7’s release squad as a lead or as a cohort, please show interest in the comments below, specifying the desired role and level of involvement (lead/cohort).


Props to @peterwilsoncc for kicking off this post, and @chanthaboune and @cbringmann for reviewing it.

#planning #6-7

WordPress 6.6 release squad ready

This post is a follow-up to the WordPress 6.6 call for volunteers update.

I’m glad to announce the WordPress 6.6 release squad is ready and the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. and Documentation lead roles have been filled:

Big thanks to everybody who volunteered to the release squad or to mentor and support!


Thanks to @chanthaboune for reviewing this post.

#6-6 #planning

WordPress 6.6 call for volunteers update

This post is a follow-up to the initial WP 6.6 call for volunteers.

Relevant Updates

  • Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. Leads: After some discussion and feedback, the proposal to experiment with merging the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Triage and Edito Triage lead roles has been reverted. As a result of this, @fabiankaegy and @colorful-tones will focus on triaging the GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ repository, and therefore, the release squad is looking for one or two Core Triage Leads to focus on triaging TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress..
  • Documentation Leads: In WordPress 6.5 it became clear that this role does need a bit of experience to enable the rest of the team’s contributions. Let’s ensure we find a Documentation Lead with prior experience to ensure they are able to handle release-specific work.
  • Default Theme Wrangler: The Default Theme Wrangler role was introduced as an experiment for 6.5 with the hopes of ensuring all default themes fully support any new features. After checking in with @poena and without any additional incoming feedback in the still-open 6.5 Release Retrospective, our recommendation is to drop the role from the squad since having the role on the squad hasn’t meaningfully impacted the default theme queue. This can be revisited in the future.
  • Default Theme Leads: As pointed out in the previous post comments, work towards the new default theme included in 6.7 should start during the 6.6 cycle. Even if not part of the 6.6 squad, folks interested in leading the next default theme in 6.7 are invited to express interest in the comments below. In particular, the first step to kick off the new theme would be to identify the theme designer(s).

Release squad as of April 23nd


Thanks to @annezazu, @chanthaboune and @poena for reviewing this post.

#6-6 #planning

WordPress 6.6 Planning Proposal & Call for Volunteers

  • Please leave your feedback about the schedule and release squad size in the comments by April 7th.
  • If you are interested in participating in WordPress 6.6’s release squad as a lead or as a cohort, please show interest in the comments below, specifying the role and the type of involvement (lead/cohort).

With WordPress 6.5 almost ready, it’s time to start planning WordPress 6.6 so that the release leads can participate from the start of the release cycle.

The timeline for the second release of 2024 takes into consideration WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Europe in June, WordCamp US in mid-September, and the observed lower number of contributors available during the northern hemisphere summer. To avoid having major milestones (Beta1, RC1) conflictconflict A conflict occurs when a patch changes code that was modified after the patch was created. These patches are considered stale, and will require a refresh of the changes before it can be applied, or the conflicts will need to be resolved. with flagship events, this proposal suggests having WordPress 6.6 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 before WCEU 2024, as the opposite would result in an even shorter release cycle for WordPress 6.7.

According to the schedule proposed below and the GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ release cadence, WordPress 6.6 would include up to Gutenberg 18.5 for a total of 8 Gutenberg releases.

Proposed WordPress 6.6 Schedule

MilestoneDate
Alpha (trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision. open for 6.6 release)March 5, 2024
Beta 1June 4, 2024
Beta 2June 11, 2024
Beta 3June 18, 2024
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). 1June 25, 2024
Release Candidate 2July 2, 2024
Release Candidate 3July 9, 2024
Dry RunJuly 15, 2024
WordPress 6.6 General ReleaseJuly 16, 2024

Please leave your feedback about the schedule in the comments by April 7th.

Release Leads call for volunteers

Having more than one lead per role has proven helpful in sharing responsibilities, especially in the case of unexpected events, and fostering leadership by pairing experienced leads with first-timers. However, recent feedback has also pointed in the opposite direction, with the squad having too many voices when combining role duplicity with the increased number of different roles. These larger squads have also fostered a bystander effect, creating the sometimes false feeling that somebody else must be working on things, resulting in unclear direction.

Since this release cycle is shorter than the last ones, I propose scaling back the release squad size again, trying to find a middle ground. Reducing role duplicity is less risky at this point as, in the event of unexpected release leadRelease Lead The community member ultimately responsible for the Release. availability, plenty of now-experienced contributors are ready to step up and lend a hand in case of necessity.

This squad reduction also includes experimenting with unifying the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and Editor Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. roles so that the Triage Leads have a wider picture of issues across the technical side and can act as a nexus between Core and Editor Tech Leads.

With this smaller release squad, release leads should have proven experience and good availability during the release cycle. Less experienced folks and newcomers are still welcome to join as a cohort.

Some folks have already volunteered in the previous call for volunteers; some roles are already filled, whereas availability has changed for some people and there are still open spots. The TBDs found in the list below indicate the number of desired vacancies to fill.

  • Release Lead: Matt Mullenweg
  • Release Coordinator:
  • Core Tech Leads: TBD, TBD
  • Editor Tech Leads: Ella van Durpe, TBD
  • Triage Leads: Fabian Kägy, Damon Cook *
  • Documentation Leads: TBD, TBD
  • Marketing & Communications Lead: TBD
  • Test Lead: TBD
  • Design Lead: TBD
  • Performance Lead: TBD
  • Default Themes Lead: TBD

* Both Triage Leads had volunteered for either Core or Editor Triage roles.

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

As a reminder, if you are interested in participating in WordPress 6.6’s release squad as a lead or as a cohort, please show interest in the comments below, specifying the desired role and level of involvement (lead/cohort).


Thanks to @jeffpaul and @desrosj for the peer review and feedback

#6-6 #planning

Call to action: 2024 major releases call for volunteers

Based on the previous proposal around the 2024 Major Release Timing, it’s time to call for volunteers. Since there are release dates for the upcoming three releases, let’s formalize the 6.5 release squad and begin shaping the other two squads of the year ahead. Knowing who will participate in 6.6 and 6.7 in advance will let folks shadow previous releases and allow for better preparation and mentoring.

WordPress 6.5 Schedule

MilestoneDate
Alpha (trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision. open for 6.5 release)October 17, 2023
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. 1February 13, 2024
Beta 2February 20, 2024
Beta 3February 27, 2024
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). 1March 5, 2024
Release Candidate 2March 12, 2024
Release Candidate 3March 19, 2024
Dry RunMarch 25, 2024
WordPress 6.5 General ReleaseMarch 26, 2024

WordPress 6.5 call for volunteers

The WordPress 6.5 release squad is still looking for diverse volunteers in every role.

Ultimately, each volunteer will only participate in a single role, and each role aims to have two to three people; past releases have shown that while it’s beneficial to share the responsibility with other people, there are diminishing returns when there are too many folks involved.

The following names are not assignments, only the summary of folks who have volunteered so far:

  • Release Coordinator: Héctor Prieto
  • CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Tech Lead: Pascal Birchler*
  • Editor Tech Lead:  Dave Smith
  • Core Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. Lead: Rajin Sharwar
  • Editor Triage Lead: Anne McCarthy*
  • Documentation Lead:
  • Marketing & Communications Lead:
  • Test Lead: Anne McCarthy*, Vipul Ghori, Patrick
  • Design Lead:
  • Performance Lead: Pascal Birchler*

(*) People who have volunteered for more than one role. Their participation will be adjusted to a single focus depending on the release squad’s needs.

As of today, every role has openings; if you are interested in participating, please leave a comment below by January 12th.

WordPress 6.6 and 6.7 timeline

These are the updated release dates for WordPress 6.6 and 6.7:

  • WordPress 6.6 Beta 1 is planned for June 4, and the general release for July 16 (no changes since the original proposal).
  • WordPress 6.7 Beta 1 is planned for October 1, and the general release for November 12. The dates have been pushed one week to consider WordCamp US 2024 (September 17-20) and give some breathing room in between.

Please bear in mind these dates are not fixed and might change as the year progresses. This early planning aims to provide clarity around the release timeline and shape the upcoming release squads in advance.

WordPress 6.6 and 6.7 call for volunteers

Since we have a rough idea of the WordPress 6.6 and 6.7 dates, let’s start shaping their release squads. Please volunteer in the comments below if you would like to participate in these releases, being mindful of your availability throughout the year before committing. Needless to say, if your availability changes later due to unforeseen circumstances, adjustments to the squads can be made.

Thanks to this early planning, we will experiment with starting the next default theme as early as 6.6, so if you are interested in working on the successor of the amazing Twenty Twenty-Four, please raise your hand in the comments.


Thanks to @cbringmann and @chanthaboune for reviewing this post.

#planning #6-5 #6-6 #6-7

WordPress 6.3 Planning Roundup

Following the planning proposal, this post summarizes the release schedule and squad composition for the next major WordPress release – 6.3. The proposal saw an overwhelmingly high number of volunteers; thank you to everybody who raised their hand to participate and help make WordPress the amazing project it is. 🤝

WordPress 6.3 Schedule

The schedule remains as originally proposed. There was some discussion around the date for 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. 2 and the US Independence Day: while the planned date stays the same, the final Beta 2 date can be adjusted by the release squad depending on the availability of contributors around that date.

MilestoneDate
Alpha (trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision. open for 6.3 release)March 9, 2023
Beta 1June 27, 2023
Beta 2July 3, 2023
Beta 3July 11, 2023
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). 1July 18, 2023
Release Candidate 2July 25, 2023
Release Candidate 3August 1, 2023
Dry RunAugust 7, 2023
WordPress 6.3 General ReleaseAugust 8, 2023

WordPress 6.3 Release Squad

Thanks once again to everybody that volunteered for the release squad! Considering all applications for the different roles, a release team has been assembled with input from project leadership to ensure all aspects of the release are properly covered.

The release team has been expanded in a few areas. In particular, the Core and Editor Triage Lead roles have been increased compared to past releases, allowing the squad to run 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. scrubs in different time zones and triage all around the world!

Unfortunately, even such a big release squad cannot accommodate all raised hands. Contributors are more than welcome to ride along with the release process on the #6-3-release-leads 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/. channel, especially in preparation for participating in 6.4 and future release squads. However, all release decisions will ultimately be the release team’s to make.


Props to @chanthaboune and @cbringmann

#6-3, #planning

WordPress 6.3 Planning Proposal & Call for Volunteers

After the successful launch of WordPress 6.2, it’s time to start planning for WordPress 6.3, and for WordPress 6.4’s women and non-binary-led release. In preparation, this post includes WordPress 6.3 proposed target dates and a call for its release squad.

The timeline for the second release of 2023 takes into consideration this year’s two remaining flagship events – WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Europe in early June and WordCamp US and the Community Summit in late August. To avoid having major milestones (Beta1, RC1) conflictconflict A conflict occurs when a patch changes code that was modified after the patch was created. These patches are considered stale, and will require a refresh of the changes before it can be applied, or the conflicts will need to be resolved. with these events, this proposal suggests fitting the release process, from Beta1 to the final release, in the ten-week window between both events.

According to the schedule proposed below and the GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ release cadence, WordPress 6.3 would include up to Gutenberg 16.1 for a total of 10 Gutenberg releases.

Proposed WordPress 6.3 Schedule

MilestoneDate
Alpha (trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision. open for 6.3 release)March 9, 2023
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. 1June 27, 2023
Beta 2July 3, 2023*
Beta 3July 11, 2023
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). 1July 18, 2023
Release Candidate 2July 25, 2023
Release Candidate 3August 1, 2023
Dry RunAugust 7, 2023
WordPress 6.3 General ReleaseAugust 8, 2023

*July 4th is the US Independence Day. Although the release schedule can’t adapt to all holidays worldwide, planning a beta release on that day would likely have a low turn of participants on July 4th, given the significant contributor presence in the US.

Please leave your feedback about the schedule in the comments by April 30th.

Release Leads call for volunteers

  • Release Coordinator: TBD
  • CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Tech Lead: TBD
  • Editor Tech Lead:  TBD
  • Core Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. Lead: TBD
  • Editor Triage Lead: TBD
  • Documentation Lead: TBD
  • Marketing & Communications Lead: TBD
  • Test Lead: TBD
  • Design Lead: TBD
  • Performance Lead: TBD

The Performance Lead was first tried as an experiment in WordPress 6.2. Although feedback collection for the WordPress 6.2 release process is still open, positive sentiment around the experiment in the #6-2-release-leads Slack channel suggests repeating the role in 6.3.

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

Join The Squad… or learn from them!

If you are interested in participating in 6.3’s release squad, please show interest in the comments below. Most roles are better shared among more than one person to distribute the responsibilities.

Folks interested in joining the upcoming all-women and non-binary release squad in 6.4 will work with a mentor. While this mentorship is not tied to the 6.3 release squad, nor do mentors need to volunteer in this release, shadowing the 6.3 release process is also recommended preparation for those being part of the following release.


Thanks to @cbringmann, @francina, for the peer review and feedback

#6-3 #planning

Preparing for the Next Women & Nonbinary Release Squad

Now that we’ve shipped WordPress 6.2 “Dolphy,” it’s time for a little planning for the other major releases this year. Volunteers are needed for the WordPress 6.3 squad (release target mid-July), especially those willing to dedicate time toward mentoring the next round of squad members. I would like to propose that WordPress 6.4 be run entirely by a women and nonbinary squad, a reprise of the historic WordPress 5.6 release, “Simone”, and training cohorts offered during 6.3 are an excellent opportunity for new contributors to prepare for the 6.4 release.

Important Note: I short-hand the release to “women and nonbinary” for easy referencing in our day-to-day collaboration, but the release squad will be open to anyone who identifies as a woman, nonbinary, or gender-expansive. All contributions are welcome as always, regardless of how you identify or what groups you feel part of. 🙂

What’s the Goal?

The primary goal of any release cycle is to ship a stable and enhanced version of the WordPress CMS that ships in scope and on time. The release date for WordPress 6.4 is tentatively slated for November, with the exact dates determined as the 6.3 timeline and the 6.4 release squad is confirmed.

Having a release squad comprised of folx we don’t typically see in technology also has a goal of increasing the number of underrepresented people who have experience maintaining, managing, and shipping software in an open sourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. project. All contributions to the release and release process are welcome.

What’s the Plan?

I would like to repeat the process we used leading up to WordPress 5.6, with some slight modifications. The WordPress 5.6 release squad had the opportunity to learn the major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope. cycle process by acting as understudies to the folx that lead the WordPress 5.5 release. The 5.6 squad was able to progressively level up their skills by watching how the 5.5 squad worked, assisting on things while guided by 5.5 leads, and finally leading a minor releaseMinor Release A 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. with assistance where needed.

  1. Prepare and Plan
    1. Gather nominations for the 6.4 team and ensure the 6.3 and 6.4 release timing works for each. Participation in 6.3 is optional, but it has been successful when others tried the process before leading the process.
    2. Confirm volunteers’ alignment to release squad roles.
    3. Identify additional volunteers for any remaining release squad roles.
    4. Gather mentors for each release squad group.
  2. Join Release 6.3
    1. Join meetings, triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. sessions, etc., and ask questions in the public #6-3-release-leads channel to feel comfortable heading into the 6.4 release.
  3. Navigate Release 6.3.x
    1. Collaborate with the 6.3 release squad to navigate a point releaseMinor Release A 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. and ask every question.
  4. Drive Release 6.4
    1. Drive the release while collaborating with some established women and nonbinary contributors as well as the 6.3 mentors.

How Can You Help?

If you would like to learn more about what participating in a release this way would mean (or want to volunteer right away!), please leave a comment letting me know. You can also feel free to DM me or any of these original supporters of WP5.6: @francina @jeffpaul @desrosj. We’re interested to hear from:

  • Anyone who wants to be a part of the WP6.4 release process.
  • Anyone who wants to be a mentor leading up to or during WP6.4
  • Anyone who has questions about how this will work. 🙂

Props to the following editors and co-creators of this post: @jeffpaul @cbringmann @daisyo @ironprogrammer @bph @desrosj @priethor

#6-3, #6-4, #planning

WordPress 6.2 Planning Roundup

Following up on the WordPress 6.2 planning proposal and based on the feedback and comments received, this post intends to summarize the release schedule and release squad composition for the next major WordPress release.

WordPress 6.2 Schedule

As a reminder, the WordPress 6.2 release cycle introduces a fourth planned 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. to accommodate WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Asia, providing an extra buffer between the event and two of the biggest release milestones (Beta1 and RC1).

MilestoneDate
Alpha (trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision. open for 6.2 release)October 18, 2022
Beta 1 & Feature FreezeFebruary 7, 2023
Beta 2February 14, 2023
Beta 3February 21, 2023
Beta 4February 28, 2023
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). 1March 7, 2023
Release Candidate 2March 14, 2023
Release Candidate 3March 21, 2023
Dry RunMarch 27, 2023
WordPress 6.2 General releaseMarch 28, 2023

WordPress 6.2 Release Squad

Thanks to everybody that volunteered for the release squad! Considering all applications for the different roles, a release team has been assembled with project leadership to ensure all areas are properly covered.

Based on the positive feedback received by the proposal of this new role in the call for volunteers for the release squad, this release will trial a new role — Performance Lead. In this first iteration, the Performance Lead will run early performance testing in WordPress trunk and act as an advisor, flagging performance regressions before they are shipped, helping solve them, and providing guidance to the rest of the release squad on performance-related discussions.

Release LeadRelease Lead The community member ultimately responsible for the Release.: Matt Mullenweg
Release Coordinators: Francesca Marano, Héctor Prieto
CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Tech Co-Leads: Tonya Mork, Jb Audras
Editor Tech Co-Leads: George Mamadashvili, Nik Tsekouras
Core Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. Co-Leads: Colin Stewart, Mukesh Panchal
Editor Triage Co-Leads: Anne McCarthy, Nick Diego
Design Lead: Rich Tabor
Documentation Co-Leads: Birgit Pauli-Haack, Femy Praseet, Milana Cap, Abha Thakor
Marketing & Communications Co-Leads: Jonathan Pantani, Lauren Stein, Mary Baum
Test Co-Leads: Robin, Adel Tahri
Performance Lead: Felix Arntz

All release decisions will ultimately be this release team’s to make. However, contributors are more than welcome to follow along with the release process on the #6-2-release-leads Slack channel.


Props to @cbringmann for peer review.

#6-2, #planning

WordPress 6.2 Planning Schedule Proposal

As we wrap 2022 with three major releases, it’s time to look ahead and start planning for the following year. In preparation, this post includes proposed target dates and a call for the release squad for WordPress 6.2, the first major release of 2023.

The first-ever WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Asia will take place in February 2023. To accommodate it and avoid having major milestones (Beta1, RC1) very close to the event, the proposed schedule consists of a 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. period consisting of four planned Beta releases, as opposed to the three planned Betas in recent major releases.

According to the schedule proposed below and the GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ release cadence, WordPress 6.2 would include up to Gutenberg 15.1 for a total of 10 Gutenberg releases.

Proposed WordPress 6.2 Schedule

MilestoneDate
Alpha (trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision. open for 6.2 release)October 18, 2022
Beta 1 & Feature FreezeFebruary 7, 2023
Beta 2February 14, 2023
Beta 3February 21, 2023
Beta 4February 28, 2023
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). 1March 7, 2023
Release Candidate 2March 14, 2023
Release Candidate 3March 21, 2023
Dry RunMarch 27, 2023
WordPress 6.2 General releaseMarch 28, 2023

Please leave your feedback about the schedule in the comments by January 10.

Proposed WordPress 6.2 Release Leads

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

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

Join The Squad!

If you are interested in being a part of 6.2’s release squad, please show interest in the comments below. Roles can be shared among more than one person!


Thanks to @cbringmann for the peer review.

#6-2, #planning