Dev Chat summary, September 14, 2022

Notes from the weekly WordPress developers chat that takes place in the #core SlackSlack Slack is a Collaborative Group Chat Platform The WordPress community has its own Slack Channel at channel.

1. Welcome

Dev chat was led by: @webcommsat and @ndiego.

This agenda was followed. Props to @webcommsat and @meher for preparation of the dev chat agenda and posts.

2. Announcements

No announcements were added to the agenda or raised in the meeting.

3. Blogblog (versus network, site) posts

Please take a moment to read them and add to the various discussions.

4. Upcoming releases

a) The next major is 6.1.

Update from the release squad members and any questions.

@webcommsat: The 6.1 Walkthrough and transcript are quite detailed and will be a useful resource for other teams including #docs #training and #marketing teams too. Well done to all involved. 

@jeffpaul: 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 is next Tuesday (September 20, 2022).

@czapla is the Editor Tech Co-lead for 6.1, and highlighted the work 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. the PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher changes from the for the 6.1 Release: CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. committers are needed to help get the backports reviewed and merged into core. You can see the ones that need attention in the “Needs review” on the project board.

Release Party for WordPress 6.1:

  • Timing: to be confirmed – it was requested that the time is added to the comments of this summary post. The time may be decided by whatever tasks remain in TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress..

@desrosj: Nothing from me! Just check out the walkthrough if you haven’t yet.

Bug scrubs

@audrasjb: will run a double 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 on September 14, 2022, to ensure to cover as many bugs as possible, 20:00-22:00 UTC. These new scrubs will be added the meetings calendar.

@ndiego: I did want to call out the Editor Bug Scrubs that are every Tuesday at 14:00 UTC in #core-editor. We will be shifting focus to all things 6.1 and could always use more attendees in these sessions.

b) Minor releases

No further updates at this stage.

c) Discussion on early timeframe

This was asked at WCUS contributor dayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of There are many teams that people can participate in, each with a different focus.

@jeffpaul and @davidbaumwald had crafted a proposal or something on that a while ago, and @clorith had volunteered to help with the post. Come back to this after Beta 1.

@audrasjb: For 6.1, I tried to stick with early = one month before beta 1, less or more.

5. Components and tickets

Component maintainers

General: @sergeybiryukov – efforts have continued on updating WordPress core and unit testunit test Code written to test a small piece of code or functionality within a larger application. Everything from themes to WordPress core have a series of unit tests. Also see regression. suite for PHP 8.1 and preparing for PHP 8.2. Thanks @jrf, @costdev, @ayesh, and everyone testing the PHP 8.2 PRs! Check tickets #55652, #55656, #55787, #56513, #56514, #56033, #56034 for more details.

Build/Test Tools, Date/Time, 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.. Permalinks: @sergeybiryukov – no major news this week.

About / Help: @marybaum will update on these components next week after her leave.

Quick/ Bulk Edit: @webcommsat – the scrub on Monday has been cancelled as it is a national day of mourning for the HM Queen in the UK. We will add a note to the bug scrub list. A new date will be added to the scrub list. 

Component maintainers, please continue to share your updates and any help you need. You can add these asynchronously to the Dev Chat agenda or to the Summary on the Make Core blog.

Tickets to raise pre-6.1 Beta 1

You can also raise any tickets that you would like to highlight for help, especially if they pertain to 6.1.

@audrasjb: For example, #55985 Twenty Twelve to Twenty Seventeen: bundle Google Fonts in each theme – this is a must have for 6.1. @sabernhardt changed it to a task to give it more visibility. Discussion on whether it should be considered a bug given the privacy implications.

6. Open Floor

No items were raised.

Props to @webcommsat for the summary and to @ndiego for review.

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