Summary, Dev Chat, Feb 19, 2025

Announcements 📢

There are no major announcements from the past 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.8

We are currently in the WordPress 6.8 release cycle. Read more about the release squad, timeline and focus for this 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: 20.3

The next Gutenberg release will be 20.3. It is scheduled for today, February 19 and will include the following issues.

Discussion 🤔

Added speculative loading support

@joemcgill mentioned that Speculative Loading was implemented yesterday and encouraged people to test the feature and provide feedback to help address any bugs before the major release. Further information on this can be found here: #62503

WordPress 6.8 Feedback

@jeffpaul asked if anyone sees an enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. or other priority topic that requires attention before 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 on March 4th, which is less than two weeks away.

Decision Needed on REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/. Template Exposition

@joemcgill mentioned that a decision is needed on how to resolve the issue in #62574 regarding where to expose default template types or template part areas in the REST API.

Editor Updates 🔄

• In the future, the Editor Update News will be published separately as individual posts.
• Let’s take a quick look at what has been happening with the Gutenberg Editor. See here.

Thank you @krupaly2k for the detailed listing and efforts based on the current development status.

Open Floor 💬

WordPress 6.8 | Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. update

@audrasjb shared updated stats for the upcoming WordPress Release 6.8 release with detailed information.

Ticketticket Created for both bug reports and feature development on the bug tracker. Status 

On the 352 tickets in the milestone:

• about 25 tickets have been moved to Future Release or 6.9 last week
• 175 tickets are closed as fixed (+15 compared to previous week)
• 177 tickets are still open (-24 compared to previous week)

---

Ticket Types

On the 352 tickets in the milestone:

• 191 are bugfixes (-3)
• 127 are enhancements (-5)
• 23 are blessed tasks (-1)
• 11 are feature requests (=)

Please note that 6.8 tries to limit the number of new features.
As we are approaching Beta 1, we’re starting to puntpunt Contributors sometimes use the verb "punt" when talking about a ticket. This means it is being pushed out to a future release. This typically occurs for lower priority tickets near the end of the release cycle that don't "make the cut." In this is colloquial usage of the word, it means to delay or equivocate. (It also describes a play in American football where a team essentially passes up on an opportunity, hoping to put themselves in a better position later to try again.) almost all tickets marked early, feature request and enhancement.

Misc infos:

• We have 0 ‘high’ priority ticket (-1): 
• On the 177 open tickets, 6 have the ‘commit’ keyword (-3)
• On the 177 open tickets, 6 have the ‘early’ keyword (-1)

To committers working on 6.8: feel free to commit any tickets that are ready to ship! Here’s the Trac report for those tickets.

For people working on early tickets, especially committers: please note that we’ve started moving some tickets to milestone 6.9 or Future Release. Here’s a useful Trac report.

The next scheduled scrub is tomorrow, February 20th, at 20:00 UTC.