Summary, Dev Chat, December 4, 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 @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, 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/ 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 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.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 coreCore 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 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. and 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)..

@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 TracTrac 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

Summary, Dev Chat, November 27, 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.

As mentioned at the top of today’s agenda, from today forward, the weekly Dev Chat times will be back to 20:00 UTC.

Announcements

WordPress 6.7.1 was released on November 21, 2024.

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.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. A call for volunteers for the release squad has been published here.

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

The next Gutenberg release will be 19.8, scheduled for December 4. It will include the following issues. Reading the release posts, like What’s new in Gutenberg 19.7 is a great way to see what is being worked on for the next major release.

Discussion

There were no topics proposed for this week. As a reminder, anyone can propose discussion topics for these meetings by commenting on the agenda posts each week or reach out to @mikachan or @joemcgill (the current CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Team Reps) directly.

Open Floor

@azaozz mentioned ticketticket Created for both bug reports and feature development on the bug tracker. #62504, which seems somewhat common judging by the number of duplicate tickets.

Was wondering if having just a hotfix pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party will be sufficient until 6.7.2 considering it would probably be released next year.

A current workaround for folks is to update the Classic Editor plugin. The same issue affects any plugins that still use the old Edit Posts screen to edit custom post types, and we recommended that these plugins apply the hotfix to work around the issue until the fix is backported to 6.7.2.

Props to @joemcgill for reviewing.

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

Summary, Dev Chat, November 20, 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.

As mentioned at the top of today’s agenda, from today forward, the weekly Dev Chat times will be back to 20:00 UTC.

Announcements

WordPress 6.7.1 is now available! Thanks so much to everyone who helped prepare this release.

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

We are currently in the WordPress 6.8 release cycle. You can review and give feedback on the proposed release schedule for 2025 on this post. A call for volunteers for the release squad has been published here.

Next maintenance release: 6.7.1

We discussed the plan to release WP 6.7.1 on Thursday, November 21, at 13:30 UTC, according to this schedule.

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

The next Gutenberg release will be 19.8, scheduled for December 4.

Discussion

@johnbillion mentioned doing some analysis of how often tickets are bumped from one major release to the next, as there are currently >200 tickets in the 6.8 milestone on Trac. @joemcgill suggested doing a scrub of the existing tickets and moving any that have been bumped more than one release to “Future Release”. We also discussed keeping an eye on how often tickets are bumped during the 6.8 cycle.

Open Floor

We started with a call for volunteers that @bph shared:

From the Developer Blogblog (versus network, site) content board we identified six approved topics that are looking for writers. Check out the issues and if you want to tackle a topic, comment on it.
For questions, join us in the #core-dev-blog channel or pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” @bph (me) .

@remy mentioned ticketticket Created for both bug reports and feature development on the bug tracker. #51525, which proposes adding two new functions, apply_filters_single_type() and apply_filters_ref_array_single_type():

we have a separate repo where we are doing the changes and testing them live in our plugins, but we were waiting for feedbacks before merging the changes up to coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.

We discussed that it would be good to look at this soon and consider it for the 6.8 release.

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