Summary, Dev Chat, October 9, 2024

Start of the meeting in 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/., facilitated by @joemcgill. 🔗 Agenda post.

Announcements

WordPress 6.7 Beta 2 was released on October 8. Thank you to everyone who contributed to this release and attended the release party! There is a helpful guide here on how to help test this release.

During the meeting, @peterwilsoncc and @marybaum updated the Playground link in the news post to correctly load WP 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. 2.

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 Beta 2 is scheduled for Tuesday, October 8. For specific release times, review the release party schedule post.

@peterwilsoncc shared that there’s been a change in the release squad. @get_dave will be replacing @noisysocks in the co-editor tech lead role. Kai will remain as the other editor tech lead. The WP 6.7. release page will be updated to reflect the addition of @get_dave while keeping @noisysocks as a listed co-lead to acknowledge his contributions to this release.

Next maintenance release

There are no maintenance releases planned at this time.

However, earlier in the #6-6-release-leads channel, @hellofromtonya mentioned…

This week, continuing to triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. tickets reported against 6.6.x (ie Version).
Then can do a 6.6.3 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. scrub in #core to help with assessment and resolutions.

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.4

The next Gutenberg release will be 19.4, scheduled for October 9, and will include the following issues.

Discussion

There were no discussion topics raised this week, so @joemcgill shared the following issues that were raised in the #6-7-release-leads channel:

From @ndiego (link):

A reminder that there are a number of bugs on the 6.7 Editor project board that need addressing. Specifically, the new Zoom Out Mode has many issues. Most are minor, but additional help on these would be great.

From @joen (link):

One issue that could use your eyes is 65644. It’s a pretty unfortunate bug, given TT5 will heavily rely on section styles. If you can help fix this issue, or know someone who might be able to, please reach out!

@peterwilsoncc asked for feedback on #59684. Specifically, wondering where where wp_save_image is tested so he can ensure he doesn’t break metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. data in an attempt to fix it. @joemcgill agreed to follow up after the meeting.

Open Floor

Brad V asked for clarity about whether PRs for default themes should be made against wordpress-develop.

@peterwilsoncc confirmed:

For the bundled themes, yes, they are maintained in WordPress-Develop.

You can open a ticketticket Created for both bug reports and feature development on the bug tracker. on https://core.trac.wordpress.org/newticket?component=Bundled+Theme if it doesn’t already exist.

And create a PR against https://github.com/WordPress/wordpress-develop/ with a link to the ticket in the description.

Props to @mikachan for proofreading.

#6-7, #core, #dev-chat, #summary