The WordPress Developers Chat meeting took place on March 8, 2023 at 20:00 UTC in the core channel of Make WordPress Slack.
Are you interested in helping draft Dev Chat summaries? You can volunteer to be added to the rotation, either during the meeting or by contacting
abhanonstopnewsuk on the Make Slack.
- WordPress 6.2 Beta 5 is available to download and test. Thanks to everyone who was involved and tested for 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. 5.
- WordPress 6.2 Release Candidate 1 has been postponed to March 9, 2023 at 17:00 UTC.
Between February 27 and March 6, 2023, there was some great work again on Trac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress.:
- 45 commits
- 79 contributors
- 63 tickets created
- 12 tickets reopened
- 61 tickets closed
- and 5 new contributors!
- Please refer to Developer Notes for 6.2 for all the new 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. released this week. It has been a very busy time for the release documentation team, so a big thanks to everyone who has helped write, review, edit, administer 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/, or anything else related to these important communications.
- The 6.2 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 expected to be published soon. Shout out to @bph, @milana_cap, @webcommsat, and @femkreations, the documentation release group, and to all those who made contributions.
Key information for 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.: 6.2
These links contain great reading material and helpful information for anyone wanting to get more involved in the release — make sure to check out the new (⭐️) items:
Also check the #6-2-release-leads channel for the latest updates.
If you would like to get involved with testing, check out the 6.2 call for testing post to get started.
Read about important accessibility improvements in this post from @annezazu, @joedolson, and @alexstine. Thank you to everyone on the 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) Team and the many other contributors who support this work.
The WordPress 6.2 preview gives focus to highlights in the release for anyone who missed the live demo or would like a recap.
Release Squad Updates
@jeffpaul asked how things look for RC1, and @webcommsat and @audrasjb confirmed that while the regression 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. in Trac #57630 was being evaluated, no additional delays were anticipated.
Requests for Help with Tickets/Blockers
@ndiego requested a call out for Gutenberg PR 48731, to address an issue from Beta 4. While developers are confident with the fix, more testing is requested — specifically to confirm that no “white screens” are seen in the editor or when using the browser Back button. Nick also asked emphasized the need for more general testing in the site editor.
@sergeybiryukov provided updates on the Build/Test Tools component:
@sergeybiryukov noted there were no updates for the Date/Time, General, I18N 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., or Permalinks components.
@ironprogrammer brought up Trac #57891, requesting confirmation of the issue from other contributors. Brian confirmed to @ndiego that the issue applied to
trunk, and not Beta 5. @petitphp reproduced the issue and provided a test report.
@sergeybiryukov and @webcommsat highlighted previous interest in running new contributor meetings in different time zones, including APAC-friendly. @sergeybiryukov shared information to help those interested: the guidelines and script link in the handbook for running such meetings. Further discussion on frequency and time(s) will be discussed amongst volunteers after the work on the current release.
@hellofromtonya asked for additional testing and investigation of Trac #57630, a regression or 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. related to child themes that use parent template parts.
The next meeting will be on March 15, 2023 at 20:00 UTC.
As a reminder, in many countries Daylight Saving starts the second Sunday of March, i.e. March 12, so your local meeting start time may be different.
Props to @webcommsat for running the meeting, and to @ironprogrammer for the summary. Review by @webcommsat.
#6-2, #dev-chat, #meeting, #summary