Agenda followed for Dev Chat for the weekly WordPress Developers Chat which included updates on 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.0.
Start of the meeting in #Core Slack
WordPress 6.0 RC2 is available for testing (released May 10, 2022). Since the RC1 release on May 3, 2022, there have been approximately 40 issues resolved in Gutenberg and Trac. Thanks to everyone involved and people who came along to test at the release party.
Gutenberg 13.2 has landed!
Early bug schedule for 6.1 – thanks @costdev. Note change of day – these will now happen on Thursdays 18:00 UTC and not Mondays.
3. Blog (versus network, site) posts of note to core Core is the set of software required to run WordPress. The Core Development Team builds WordPress.
A Week in Core – May 9, 2022 (published May 11, 2022) – thanks to @audrasjb
Performance Team Meeting Summary, May 10, 2022 – includes some updates on WebP, some POCs needed for the Site Health and Measurement sub groups. At the end of the post, there is a list of areas where help is needed.
Open floor item in the Editor Chat agenda for May 11, 2022 on a discussion around adding a new label to the 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/ repo around issues that impact adoption. The aim would be to have an easier way to see, at a glance, what big issues are impacting the adoption of Gutenberg.
Full Site Editing Program Testing Call 14 – Rallying Recipe Reviewers. Deadline for feedback: 18 May 2022
4. Upcoming releases
Next major release: WordPress 6.0
Update via @annezazu
No big updates to share on 6.0 — the release squad is really crushing it and things are moving forward as expected. Some quick updates to be safe though:
- The 6.0 video continues to progress nicely and is on track to ship the day before the release still.
- Props are in progress thanks to a wonderful effort by @desrosj.
- A 6.0.1 board has been started so we carry momentum into the point 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.: https://github.com/orgs/WordPress/projects/31
Thank you to everyone who is making this release possible. Please keep testing and, if you can’t, encourage others to do so. It all helps.
Update via @costdev on bugs scrub and testing side: Monitoring new tickets regularly and things are going well.
6.0 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). 3
6.0 RC3 Release Party on May 17, 2022, 16:00 UTC
Meet in the #core 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. As always with releases, there’s a chance this time may change the day of depending on how things are progressing. The time will be communicated across channels (#core-editor, #6-0-release-leads, and in #core). All welcome.
The next major 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. scrub before RC3 will be on Thursday May 12, 2022, 21:00 UTC. The full bug scrub schedule for 6.0
Recap of useful resources on 6.0
5. Open Floor
If you are a component maintainer or running a bug scrub and have any updates not already mentioned under 6.0 updates, you can raise them in this section too.
a) Component maintainers – items of note
Update from @sergeybiryukov
Build/Test Tools: The local development environment can now run on Apple M1 machines without requiring local configuration changes. Ticket Created for both bug reports and feature development on the bug tracker. #52356 for more details.
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.: An edge case was fixed in the script loader where the dependency order was incorrect for scripts with translations in some cases. Ticket #55628 for more details.
General, Date/Time, Permalinks: No major news this week.
b) WordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Europe Contributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/., June 2, 2022 – core tables.
Update from @desrosj: If anyone will be at WCEU Contributor Day and has a specific topic they would like to focus on for the day at the Core tables, please share the topic and a brief one or two sentence description by Friday. I have a few generic topics, but if anyone is looking to lead specific discussions, please send them over!
@marybaum: later in the summer, there will be similar planning for WordCamp US.
c) Rubber duck emoji request! It all happens at dev chat!
d) @clorith brought up Ticket Gutenberg 40316 and the issue of experimental APIs versus backward compatibility. A lively discussion followed, with several suggestions on how to get input from the community at large. (Note from Core Team rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. @marybaum: If you’re new, dev chat is not a forum for making final decisions. But it is a great place to surface topics that warrant wider discussion, and to explore where those conversations should start).
Props to: @webcommsat for writing the summary, @marybaum for reviewing.