Dev Chat Summary, November 15, 2023

The WordPress Developers Chat meeting took place on Wednesday, November 15, 2023 at 20:00 UTC in core on Make WordPress Slack (or #core in Matrix).

Key info


🎉 WordPress 6.4.1 is out!: Thank you to every single person who has been involved and continues to contribute to 6.4! (Also see the original release post.)

Additional background information on the release:

Highlighted Posts

@webcommsat emphasized that developers with 6.4 knowledge can really help with reviews and contributions toward End User docs. The sooner the documentation is published, the sooner it can benefit the community.

And some items from last week’s cancelled chat to touch on:

@jeffpaul called on potential 6.5/6.6/6.7 leads to share their thoughts on this post.

  • Accessibility improvements in the 6.4 release: Check out this rundown of a11yAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). ( items addressed in 6.4.
  • Proposal to discontinue the weekly #core-editor meetings: Add your thoughts about this change, and opportunities to incorporate editor discussions in Dev Chat.
  • Shareable performance testing utils: Join the discussion to explore ways that projects can incorporate performance testing as part of their development workflow.

And finally, some reminders ⏲️:

  • Call for 6.4.x Release Managers: Work on improving 6.4 continues after the main release, so please consider joining the 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. squad to help keep 6.4 healthy.
  • Call for volunteers to help with 6.4 end-user documentation: The Docs team is looking for volunteers to revise end-user docs (HelpHub) for 6.4. Check out the post and learn how to pitch in! Wait…did I mention this already? Yep — but it’s so important for our user community ❤️.

Release Updates

Next minor release: 6.4.2

@jeffpaul noted that if minor release squad volunteers can be found soon, that there’s a possibility of shipping a 6.4.2 minor release before year’s end. He requested feedback on whether there are any urgent/important items that need to be addressed soon.

@jorbin has been watching the (6.4) minor release issues report, and noted that #59847 seems the most urgent. He also pointed out nice-to-have editor package backports in #59828. If volunteers can be found to support the release, then he suggested a target of the week of November 27, 2023.

@joemcgill noted that #59847 is nearly ready, and requested feedback on the related PR.

👉🏻 Volunteers who can help with the 6.4.2 minor release (and determine timing) should drop a note in #6-4-release-leads.

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

  • The development cycle page has been created. It will be populated after discussing release timings and the finalization of the squad.
  • Are you able to help with future 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. scrubs? Check out the 6.5 scrub schedule.
  • And keep tabs on the #6-5-release-leads channel for additional updates.

@jorbin asked that 6.5 ticketticket Created for both bug reports and feature development on the bug tracker. scrub participants keep an eye out for regressions that should be moved to the 6.4.2 milestone, to get fixes delivered to users more quickly.

@webcommsat shared a link to the November 14 scrub for anyone looking at tickets async, and called on contributors to help with patches and writing of tests. 🙏🏻

Open Floor

Proposal to Cancel #core-editor Meetings

(This discussion started during highlights with regards to this proposal, and is shared here for readability.)

@jeffpaul expressed worry about losing touch with 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. development without regular meetings and sought alternative ways to stay updated. @jorbin suggested incorporating editor updates into existing meetings, particularly emphasizing involvement from major release editor leads.

@webcommsat highlighted the usefulness of core-editor summaries and proposed integrating regular updates into the dev chat agenda. @ironprogrammer raised the question of where the editor summary would originate if the meetings themselves were cancelled. @jeffpaul suggested obtaining editor updates during dev chat to ensure communication of updates and blockers across the project.

The idea of carving out an official “editor updates” section in dev chat was considered, and @jorbin suggested seeking volunteers from the #core-editor channel to participate in the chat. @annezazu volunteered to take on the responsibility and discussed potential ways to share editor updates, including during the meeting or through agenda posts. The need for asynchronous options, given different time zones, was acknowledged.

@webcommsat suggested having a dedicated section for editor updates on the dev chat agenda post, and plan for asynchronous sharing. @annezazu volunteered to make the meetings and incorporate asynchronous sharing, considering her near term availability across time zones. The importance of avoiding disruptions during meetings was discussed, as was the possibility of maintaining #core-editor office hours for specific questions related to the editor.

2024 Core Team Reps Nominations

@webcommsat gave a reminder for #core contributors to have a look at the draft post: Nominations for Core Team Reps: 2024 Edition. The dates/timing may need revising, and team reps are looking into the possibility of having the voting poll embedded into the post to make it easier to vote. Please share your feedback in #core and CC @webcommsat and @hellofromtonya.

WordPress 6.4 Retrospective

@cbringmann shared WordPress 6.4 Retrospective, and asked that anyone who has contributed to the release to reflect and share their thoughts on the release process (instructions in the post). A follow-up post will be published in December.

Next Meeting

The next meeting will be on 22 November 2023 at 20:00 UTC .

Are you interested in helping draft Dev Chat summaries? Volunteer at the next meeting!

Props @webcommsat for collaboration on this post and meeting preparation.

#6-4, #6-5, #dev-chat, #meeting, #summary

Dev Chat Summary, November 1, 2023

The notes from the weekly WordPress developers chat which took place on November 1, 2023 at 20:00 UTCin the core channel of Make WordPress Slack.

Key Links


WordPress 6.4 Release Candidate 3 was released just before Dev Chat – please help test and make the release the best it can be. All details are on the post. Thanks to everyone who contributed towards this.

Reminder: Dev Chat continues at 20:00 UTC throughout the year and does not change with daylight saving changes.

Highlighted Posts

A recording of the Hallway hangout on performance improvements in WordPress 6.4 is now available. The main points are also summarized on the post for anyone not able to access the recording.

Call for 6.4x release managers – this followed a discussion in Dev Chat last week. Please add a comment to the post if you are interested in supporting the maintenance and minor releases. Thanks to @jorbin for putting this together.

Reminder: Call for contributors to assist with 6.4 End User documentation. Extra assistance will be appreciated to help with this as we move towards the release day.

What’s new in Gutenberg 16.9.

Release Updates

Next major WordPress release: 6.4

Release candidates and rest of the cycle

RC3 was the last scheduled 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)..

@hellofromtonya explained that another 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). could possibly happen in the following circumstances. If a regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5.(s) gets reported and resolved, then yes, another might happen. But currently all regressions are resolved and shipped in RC3!

Next week’s schedule:

  • Dry Run – on Nov 6, 2023.
  • 24 hour code freeze starts after the Dry Run.
  • 6.4.0 release party starts on Nov 7, 2023 after the 24 hour code freeze expires.

Any issues relating to 6.4?

No other issues were raised during the meeting.

Relevant 6.4 links

No new links were published at the time of the meeting.

Field Guide for 6.4

@webcommsat: In addition to the Field GuideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page., you can also find all Developer Notes relating to 6.4 using this tag. If you think a change would benefit from an additional dev notedev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase., please add it to the Documentation Tracker for 6.4. You can also tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.) one of the docs release co-leads in a message in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. if you want to discuss the possibility of an additional dev note and do not have access to the tracker.

Release parties schedule for 6.4

6.4 Release Candidates phase

This detailed guide will walk you through testing features in WordPress 6.4.

Roadmap to 6.4 – this release is scheduled for November 7, 2023.

6.4 Development Cycle

Future releases: 6.5

Timings and squad

  • @joemcgill followed up the question at last week’s dev chat on the formation of a release squad for 6.5.
  • @chanthaboune is thinking through the timing of releases across the year, and therefore there is no clear date for the first release of 2024 as yet. She hopes to bring a draft of suggested dates/ times by Monday November 6, 2023. This is the ‘only blockerblocker A bug which is so severe that it blocks a release.’ for a call for volunteers. One person has contacted Josepha so far to participate in 6.5.
  • General agreement in the meeting for early planning for the next release.
  • the discussion on Slack.

Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. tickets for 6.5

  • @oglekler requested triages to start as soon as possible, as 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. is already open and 6.5 Alpha has begun. She raised a call for volunteers.
  • discussion followed on updating the core handbook to reflect that triages and 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. scrubs can be held at any time, and to clarify that any contributors wanting to run a scrub did not need to wait for a completed release cycle or for a squad to be formed. The possibility of a post highlighting and calling for volunteers was suggested for the future.
  • a number of experienced core developers are able to buddy or give advice to help anyone less familiar with running scrubs.
  • if you can volunteer to run a scrub, you can share details in a future dev chat or comment on the summary post, and also post the information in the Core SlackSlack Slack is a Collaborative Group Chat Platform The WordPress community has its own Slack Channel at channel ahead of time to best ensure that others are aware and can gather to help at the scrub. The core triage lead or the Core Team Reps can also update the bug scrub post in Make/Core.
  • if you are wanting to run a scrub related to particular component(s), please contact the component maintainers who can help and share information on priority tickets or planned scrubs.

The full discussion on triaging and bug scrubs.

Tickets or components help requests

No tickets were mentioned in the meeting.

Open floor

Reminders for the following were brought up right before the meeting ended:

Call for contributors to assist with 6.4 End User documentation. Volunteers can also post in this thread from the meeting.

Call for 6.4x release managers

Next meeting

The next meeting will be on Wednesday November 8, 2023, at 20:00 UTC.

After Dev Chat posts for attention:

Hallway Hangout: Issues Triage Extending Gutenberg – note this will take place on November 10, 2023 at 16:00 UTC.

Are you interested in helping draft Dev Chat summaries? Volunteer at the start of the next meeting on the #core Slack channel or contact one of the Core Team reps.

Props to @zunaid321 for contribution to the notes, and to @marybaum for review.

#6-4, #6-5, #dev-chat, #meeting, #summary