Dev Chat summary: Wednesday, November 16, 2022

The weekly WordPress developers chat meeting was held in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. channel of the Make WordPress 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/. at 20:00 UTC.

Start of the meeting in Slack.

Announcements

Slack link.

WordPress 6.1.1 landed yesterday!

Nominations for 2023 Core Team Representatives are now open. The deadline for nominations is December 2, 2022.

Blogblog (versus network, site) posts of note

Slack link.

No other blog posts were shared.

Upcoming releases

Slack link.

For those new to dev chat, this is where any updates on the releases are shared.

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

WordPress 6.2 Development Cycle. This will be the first major release of 2023. 6.2 is in alpha and tickets are still early.

The next minor releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality. is 6.1.2

Due to upcoming holidays, these timelines were discussed:

6.1.2 planning post: mid-December 2022 or January 2023

6.2 planning post: January 2023

2023 planning post: January, likely ahead of the 6.2 planning post

Components and tickets

Slack link.

a) Components

For anyone new, there is a help / ticketticket Created for both bug reports and feature development on the bug tracker. update section each week in dev chat. Contributors can add requests to the agenda post for tickets they would like to highlight. If a maintainer can not make dev chat, they can also share their updates on the agenda.

If you are a maintainer, it is really helpful to share news about your component in dev chat live or on the agenda post. It is also a chance for all your efforts to be shared and to ask for more people to review a particular item.

No major news this week for these components:

  • Build/Test Tools
  • Date/Time
  • General
  • 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
  • Help/About
  • Quick/Bulk Edit

b) Tickets

None were raised.

Open Floor

Slack link.

a) Removing functions during release candidates

This comment on the agenda post was discussed. It asserts that this 10/24/22 release candidate commit (54682) removed the reset() function, and asks for removing functions during release candidates to be disallowed – if it’s not already.

In the replies that followed, it was mentioned that when release candidaterelease 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). methods or functions are changed, developers using them for tests could be sent a warning email, and that it could help if to use function_exists() to confirm functions are still available.

Props to @marybaum for leading the meeting, @davidpotter for writing the summary and to @davidbaumwald for reviewing, and to @webcommsat, @marybaum, @bph, @jeffpaul, @sergeybiryukov, @elrae, @joedolson, @desrosj, and @hellofromtonya for participating.

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