Summary, Dev Chat, August 17, 2022

Weekly WordPress Developers Chat – start of the meeting on Slack.

1.Welcome

Agenda
Last week’s summary.
Writing the summary is a great way of following dev chat, so do volunteer if you would like to get involved.

2. Announcements

Gutenberg 13.9 has landed! Well done to everyone involved.

3. Blogblog (versus network, site) posts of note!

The month in WordPress.
All about the next default theme:

A week in Core.
Please join this conversation about merging experimental APIs by September 7. (An audit of those APIs.)
Gutenberg is standardizing the way contributors name npm scripts. Should CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.?

4. Upcoming releases

a) The 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. is 6.1.
Helpful links:
The development cycle.
The bug-scrub schedule, and the Handbook on bug-gardening.

@audrasjb reminded the group that there’s very little more than a month left 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, so the Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. leads will do a final scrub of tickets marked “early” in order 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.) them to the next milestone.

With that he brought up tickets #22176 and #36308 and pinged their owners, @JonnyHarris and @antpb for immediate action.

@audrasjb: linked this Trac report for early tickets.

b. 6.0.2 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). and Final Release Party Dates 
@webcommsat reposted this @annezazu update from the 6.0 channel:
After finalizing with @sergeybiryukov, the following dates are confirmed for 6.0.2:

  • RC on August 23, 2022
  • Final on August 30, 2022

Release parties will be in #core around 16:00 UTC (the time we’ve been holding release parties) with wrangling here in #6-0-release-leads as needed. Hope to see you all there.

@audrasjb raised a question about changesets already merged to trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision.: Should committers start to backportbackport A port is when code from one branch (or trunk) is merged into another branch or trunk. Some changes in WordPress point releases are the result of backporting code from trunk to the release branch. those to branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch". 6.0?  

The discussion on Slack

5. Components and tickets

@sergeybiryukov:

Build/Test Tools: The Memcached container was moved into the Docker Compose config. This allows a developer to use the persistent Memcached object cache on their local development environment via the LOCAL_PHP_MEMCACHED environment variable. See ticketticket Created for both bug reports and feature development on the bug tracker. #55700 for more details.

Database: Better compatibility with MySQLMySQL MySQL is a relational database management system. A database is a structured collection of data where content, configuration and other options are stored. https://www.mysql.com/. 8.0: #49364 and #51740 for more details.

General: New helper functions for required field indicator and message, for better reusability: #54394 for more details.

Login and Registration: New is_login_screen() function helps check whether the current request is for the login screen: #19898.

I18Ni18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see localization. Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill.: New WP_Textdomain_Registry stores text domains and their language directory paths: #39210.

Thanks everyone who worked on those tickets! 

Date/Time, Permalinks: No major news this week 

@webcommsat and @marybaum:
In Help/ About:

#56357: New ticket opened for the About Page for 6.1, to add it to the milestone

In Quick/Bulk Edit:

  • #41494: further tests requested to replicate the issue. Number of tests done to replicate have not returned same result. If anyone is still facing the issue reported, please update the ticket.
  • #16502: Continues in review.
  • #52501: Will raise again with #polyglots

6. Open floor

@webcommsat: Not directly core related, but there are lots of ways to depict code and development in photographs. Look out for a post tomorrow on the Photos blog for a challenge for World Photography Day.
 

Props to @webcommsat and @marybaum for the summary.

#dev-chat, #summary