This weekly WordPress Developers Chat takes place in the #Core 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/. on Wednesday May 4, 2022 at 20:00 UTC. All welcome.
Dev Chat summary from the meeting on April 27, 2022 – @webcommsat
WordPress 6.0 Release Candidate 1 (released on May 3, 2022). This was the hard string freeze for the 6.0 and branch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch". for the release.
WordPress 6.0 Beta 4 (released on May 2, 2022).
Early focused meetings will take place on Mondays at a revised time of 18:00 UTC.
What’s New in Gutenberg 13.1 (April 27, 2022).
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.
Key links for 6.0 and updates from the squad will be in the agenda item 4, after these blog posts.
A Week in Core – May 2, 2022
Full Site Editing (FSE) Outreach Program Testing Call 14: Rallying Recipe Reviewers (April 28, 2022). Leave feedback by May 18, 2022
4. Upcoming releases
Next major: WordPress 6.0
Updates from Release Co-ordinators and members of the squad.
Useful resources/ calls for testing
5. Open floor
If you have any items for Open Floor, please add them in the comments below.
If you are a component maintainer and wish to raise a ticket Created for both bug reports and feature development on the bug tracker. in dev chat or give an update, you can also add information in the comments section.
Could you help with writing the summary from dev chat for a future meeting? Comment below or message core team reps @marybaum and @audrasjb in the Core Slack channel.
Props to: @webcommsat and @marybaum for working on items for the agenda.