Summary, Dev Chat, Jan 22, 2025

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.

Announcements

The Nominations for 2025’s Core Team Reps are now open! Please nominate people in the comments of that post. Self-nominations are welcome. The deadline is January 31, 2025.

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 maintenance release: 6.7.2

A release schedule for 6.7.2 was announced earlier today. Currently the release date is February 11. Review the next minor release milestone.

A 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 was held just a few hours ago and all tickets on tracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. for the 6.7.2 release were reviewed. One area that I could use some help with is reviewing all the tickets on GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/. https://github.com/orgs/WordPress/projects/232.

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

Gutenberg 20.1 was packaged earlier today, including the following issues. The team is currently addressing an issue that blocked the release from being published and the release will be delayed until tomorrow.

Discussion

Proposal: Moving Dev Chat starting next week, January 29, 2025 to 15:00 UTC – Based on conversation last week, and feedback from the release squad availability, it is proposed that we change the time of Dev Chat meetings for the 6.8 cycle to 15:00 UTC. Unless there are any new objections, this updated time will be reflected in the next Dev Chat agenda.

WordPress 6.8 Bug Scrubs – We have two bug scrubs each week scheduled in #core (on Mondays and Thursdays), and other ones in various channels like #accessibility, #core-editor, etc. The next one will be held in #core tomorrow at 20:00 UTC. See the 6.8 bug scrub schedule blogpost for more info.

Anyone is welcome to run a scrub, just let @audrasjb know if you’re interested in running one (or more) and he’ll add it to the schedule.

WordPress 6.8 Release Roadmap update – @krupaly2k is working on putting this together and had some follow-up questions.

  • There are some open iteration issues, are we planning to work on those for WordPress 6.8? @joemcgill asked @mamaduka to review and follow up.
  • There are two issues in the milestone related to PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher compatibility
    • #59231 – Prepare for PHP 8.3: @joemcgill and @desrosj will review and see if there are any follow-up tasks planned for this release.
    • #62061 – Prepare for PHP 8.4: @johnbillion is planning to split out remaining tasks and close this issue. No major work is planned.

Syncing Gutenberg updates 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. – We’ve been discussing trying to do this sync earlier this cycle once GB 20.1 is released.

  • There are a number of PRs listed in this GB issue that need to be reviewed in order to help facilitate that process.
  • There’s a bug with the sync command, that needs to be addressed: #62839

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