Start of the meeting in Slack 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 @mikachan. 🔗 Agenda post.
As mentioned at the top of today’s agenda, the weekly Dev Chat times have gone back to 20:00 UTC.
Announcements
The WordPress 6.8 call for volunteers is open until December 6. You can find out more and volunteer for any of the roles here.
Also, Gutenberg 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/ 19.8 was released earlier today 🎉. What’s new in Gutenberg 19.8?
Forthcoming releases
There is a proposal open for the 2025 major releases. The date for feedback has now passed, but comments will remain open until the official announcement is made. @priethor is waiting for the 6.8 call for volunteers to end before publishing an announcement with the 6.8 calendar.
Next major 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.8
We are currently in the WordPress 6.8 release cycle. You can review the next major release milestone.
The call for volunteers for the 6.8 release squad is open until Dec 6. The most pressing needs are still for Editor Tech Lead and Documentation.
Next maintenance release: 6.7.2
There is currently no release date planned for WordPress 6.7.2. You can review the next minor release milestone. @desrosj suggested that mid to late January is a good ballpark at the moment, as there are no urgent issues after 6.7.1.
Next Gutenberg release: 19.8
Gutenberg 19.8 was released prior to this meeting. See, What’s new in Gutenberg 19.8?, for details.
Discussion
@azaozz expressed his hope that every Gutenberg release can be merged to core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. during alpha. Would probably reduce the final pressure during beta 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. and RC 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)..
@joemcgill agreed, stating, “It is currently not ideal that nightly WordPress releases aren’t really available to test features that are ready until after the first sync of the cycle”.
@priethor asked, “What’s preventing us from doing that from the core side?”
Consensus from those in attendance was that there wasn’t any specific blockers to doing this, so it may be worth giving this a try in 6.8 once a release squad is identified.
@mikachan asked if we could automate a lot of the process, perhaps open a wordpress-develop PR from a GH action when a new Gutenberg release is out, and then the majority of the work would be testing and committing.
@johnbillion identified a couple of tickets on Trac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. for automation that could use help moving forward: #60967 and #60966.
Open Floor
@annezazu shared the following update prior to the meeting:
It would be awesome to have more contributors working on exposing the Font Library for classic themes, especially as work continues around adding a stylebook screen for classic themes. In this way, we can work towards landing a cohesive “Design” section for classic themes complete with patterns, Style Book, and the Font Library.
@ironprogrammer shared an updated proposal to reconsider adopting the WP Consent API.
Props to @mikachan for reviewing.
#6-8, #core, #dev-chat, #summary