Summary of the WordPress developers chat meeting in the Core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Slack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel.
Start of the Dev Chat meeting on the Core Slack
Dev Chat agenda followed – thanks to @webcommsat for preparing.
- WordPress 6.4 Beta 3 is available: Please help test and make the release the best it can be! Thanks to everyone who contributed toward Beta 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. 3, as well as those who came and facilitated the release party on October 10. Note the Twenty Twenty Four images issue has been resolved, and the images are rendering correctly in Beta 3.
- The WordPress 6.3.2 minor 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. has moved to tomorrow, October 12, 2023 (more information under release updates to follow).
- Four Weeks in Core: Many thanks to @audrasjb for this update covering the amazing activity in Trac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. between September 4 and October 9, 2023:
- 269 commits
- 337 contributors
- 295 tickets created
- 43 tickets reopened
- 277 tickets closed
- Reminder: Hallway Hangout: Working session on consolidating various navigation modes: Taking place on November 15, 2023 at 16:00 UTC. This is part of efforts to improve accessibility 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). (https://en.wikipedia.org/wiki/Accessibility) in the Site Editor.
- The Dev Blog is looking for a writer for the following topic: How to add commands to the command palette. Please respond on the GitHub 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/ ticket Created for both bug reports and feature development on the bug tracker. if you are interested.
Next major 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.4
Release 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). 1 is scheduled for next Tuesday, October 17, 2023.
This hallway hangout is happening tomorrow, October 12, 2023: What’s new for developers in WordPress 6.4.
Stay in the loop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop. with 6.4 by following:
6.4 tickets that need attention
@rajinsharwar highlighted #52529 and requested testing of the patch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. to see if they can replicate the errors mentioned.
Dev Notes 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.
@webcommsat for the release documentation group: A reminder that the Field 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. is due to be published next week. This is so the link can be included in the release’s About Page. It would be great to have as many dev notes ready in draft as soon as possible, so they can have a final review and be published.
6.4 dev notes tracking project board for reviews and publishing is in progress.
Gutenberg 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/ – Some Gutenberg tickets have already been labelled and clustered. There is a significant list that is being clustered and labelled, and these will then get added to the documentation tracker for 6.4. The tracker will show the edit, review and publish status of the dev notes – the view that will be most useful for this is ‘dev notes’. For Gutenberg, the wrangling and discussion on clustering and inclusions will happen in the Gutenberg tracker. Thanks to @bph who is going to be helping with this.
Core – If you are a component maintainer, and have not already shared that you are working on a dev 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. relating to a Core Trac ticket or cluster of tickets, please add a comment on this issue and link any google docs, and we will populate the tracker with this.
For End user and Core tickets, the labelling is continuing. As we are being advised of dev notes needed or in progress by maintainers, they are being added to the documentation tracker.
For performance dev notes, issues are being added to the documentation tracker once confirmed for reviews and publishing purposes. Wrangling and discussion of inclusion of tickets is happening on the Performance GitHub ticket.
Reviews – If any devs are able to assist with technical reviews of dev notes if needed, let @webcommsat know to update the list.
Next minor release: 6.3.2
- *A note on the 6.3.2 release schedule change:* In order to accommodate the need for hosts to deal with an important curl 8.4.0 security release on Wednesday, the 6.3.2 final release has been moved to Thursday, October 12, 2023.
- Thanks to everyone who led, supported, helped test, raised issues, and helped to fix tickets in these releases!
Gutenberg 16.8.0 shipped during dev chat. An update on this release will be published soon and will be findable on the tag 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.) #gutenberg-new on the Make/ Core blog (versus network, site).
Component Maintainers requests
@rajinsharwar highlighted Trac ticket #55335. Requested confirmation if it should be considered a bug 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..
No additional items were raised. A reminder of the Field Guide and dev notes was shared.
Props to @webcommsat for the agenda and summary, and to @ironprogrammer for facilitating the meeting and reviewing the summary.