Summary, Dev Chat, August 28, 2024

Announcements

There were no announcements this week.

Forthcoming Releases

Next 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.: 6.7

We are currently in the WordPress 6.7 release cycle. 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 is scheduled for Tuesday, October 1.

The bug scrub schedule was published prior to the meeting.

Next 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.: 6.6.2

The next maintenance release will be WordPress 6.6.2. RC1 is scheduled for Sept 4, and the full release is planned for Sept 10. See the Trac milestone for the release.

Next 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: 19.1

The next Gutenberg release at the time of the meeting was 19.1, which was released on August 28.

Discussion

The first topic was, “which releases can be done during normal working hours for our CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Tech leads?”

@joemcgill referenced this comment on the agenda post and asked @peterwilsoncc to clarify the what was being considered.

I saw a comment in the 6.7 channel that release parties are also apparently going to happen in APAC times? I’d like to know if this was discussed in public somewhere. I know moving Dev Chat was discussed, but I (as 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). for 6.7) wasn’t included in the discussion about moving the release parties, neither before or after I accepted the role.

To summarize @peterwilsoncc response:

• Beta release parties can happen during APAC sunlight
• RCs will need to happen at around the usual time (~16:00 UTC) to allow for increased attendance
• For the betas, @peterwilsoncc can drive MC and @kirasong and @noisysocks could do release commits
• During RC, MC and commits will need to be people off the release squad

@joemcgill:

I’ll note that the time you’re suggesting for betas is well out of timezone for David who is the release coordinator. According to the handbook the first responsibility of the release coordinator is to “Run various release processes in Slack (beta, 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)., release)” but whatever you all work out seems fine.

@peterwilsoncc agreed to coordinate with the release squad about release timing will publish a post announcing the timing of release parties.

Next, @kirasong shared a list of issues that had been highlighted in #6-7-release-leads as things that folks can get involved with.

@noisysocks reminded that the Iteration/Tracking Issues column in the Editor tasks board is the best source of truth re. current initiatives.

Open Floor

We discussed the following issues:

• https://github.com/WordPress/gutenberg/issues/64149 – @noisysocks agreed to add this 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. to the 6.7 board
• https://github.com/WordPress/gutenberg/issues/56181 – @noisysocks said this issue needs more discussion
• https://github.com/WordPress/gutenberg/pull/63915 – @noisysocks pinged Lena Morita, who was previously working on this issue