Notes from the weekly WordPress developers chat held in the core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. channel of the Make 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/..
The start of the meeting on Slack.
@marybaum and @webcommsat led the weekly WordPress developers chat meeting on this agenda.
Last week’s summary – September 28, 2022.
WordPress 6.1 Beta 3 landed on Tuesday, October 4, 2022. Props to everyone who helped and came to test at the release party.
3. Blog (versus network, site) Posts of Note
4. Upcoming Releases
The 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. is WordPress 6.1. For more information on the release, visit the WordPress 6.1 Development Cycle page. This includes links to the 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. as they are published, and the next 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. scrubs that are taking place and where you can join to help progress tickets.
The first 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). for 6.1 is expected to land next Tuesday, October 11, 2022.
@audrasjb gave a triage update.
On the 488 tickets in the milestone, there are:
@webcommsat: In the release documentation teams and for Learn WordPress, we are working on items to support the release. There are still lots of opportunities for people to help in both areas. @bph has also reached out to component maintainers about dev notes or items for 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.. Please do reply to her as soon as you can.
Check-in on update on the Early time frame discussions following the discussion at Dev Chat on September 14, 2022. @clorith advised that they had a quick discussion to align thoughts and points. There were a few differing opinions on some timeframes, but they should be able to put together a proposal for make/core at least before 6.1 is out.
5. Maintainers and Tickets
a) Component Maintainers updates
@sergeybiryukov provided a Build/Test Tools update:
- WordPress core unit tests now pass on PHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 8.1 and 8.2. While full compatibility with PHP 8.1 and 8.2 is still a work in progress, this should prevent new PHP issues from being introduced in WordPress core. All remaining known issues are deprecation notices. Massive props to @jrf for continuous work on PHP 8.x compatibility for many months. Tickets #55656 and #56009 for more details.
- PHPCS PHP Code Sniffer, a popular tool for analyzing code quality. The WordPress Coding Standards rely on PHPCS. results are now displayed in 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/ Action logs, making it easier in case of failure to find and understand what is causing the issue. Thanks @jrf and @desrosj. Ticket Created for both bug reports and feature development on the bug tracker. #55652 for more details.
@afragen updated Trac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticket #56650, in the General component, following last week’s discussion.
@webcommsat provided a About/ Help and Quick Edit/ Bulk Edit components update on behalf of herself, @Nalini, and @marybaum. They have continued to do a weekly focus on tickets in these two components. Everyone is welcome to join in.
- Commented and closed Trac ticket #55549
- Trac ticket #19859: further input requested for a way forward
- Trac ticket #41833 Suggest for 6.2 earlies if possible, welcome more people looking at this
- Trac ticket #50886, which has a new commentary
- added to the About page discussions, including making some suggestions on 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) tickets to highlight.
- Trac ticket #19859 – welcome some additional views on this ticket for earlies 6.2 if possible as it has not been possible for 6.1 . This would be really good to land.
- A number of other tickets are in progress of review
b) Tickets to highlight
@pbearne spotlighted #53634 with the hopes of the ticket making it into 6.1. The ticket is part of the Users Component.
@webcommsat thanked everyone involved in getting #32747 under the Administration Component through yesterday so that the ticket makes it into 6.1.
@webcommsat: the team continues to look at ways to make it easier for component maintainers in other timezones to dev chat to share updates. Each week, maintainers can also add tickets and asynchronous updates on components to the published dev chat agenda. If maintainers reading this in the summary think a drop-in for maintainers at an earlier time, held every few months, would be useful, @marybaum is collating ideas for a session after the 6.1 release lands.
If you find a component that does not have a maintainer listed in an area you would love to help move forward, talk to the Core Team Reps about it.
5. Open Floor
Nothing was raised during open floor. Next meeting: Wednesday October 12, 2022 at 20:00 UTC
Props to @webcommsat for meeting prep, @marybaum and @webcommsat for facilitating, and @marybaum, @webcommsat, and @ndiego for collaborating on the summary.