Dev chat summary, October 12, 2022

Welcome!

The WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:

Found a bugbug 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.? Create a ticket in the bug tracker.

Want to contribute? Get started quickly with tickets marked as good first bugs for new contributors or join a bug scrub. There’s more on the reports page, like patches needing testing, and on feature projects page.

Other questions? Here is a detailed handbook for contributors, complete with tutorials.

@marybaum and @webcommsat led the meeting on this agenda.

1. Welcome

If you’re keeping track, here’s the summary from October 5.

2. Announcements

WordPress 6.1 RC1 arrived on Tuesday, October 11.

@marybaum announced the impending arrival of grandson Leo Graham Mullen, who wound up being born at 22:41 UTC in New Jersey, USA.

3. Blogblog (versus network, site) posts of note

A Week in Core, from @audrasjb

What’s new in Gutenberg 14.3?

The WordPress 6.1 Field Guide gathers all the dev notesdev 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. from the release in one place. The bulk of them are in the Guide now, but often several notes get added on or slightly after the launch.

4. Upcoming releases

The next major is WordPress 6.1.

RC1 is a very nearly finished version of the software and imposes two conditions on contributors:

A hard string freeze, with the exception of very specific parts of the About page. @ryelle explained in some depth.
Commits require the approval of two CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. committers.

@audrasjb gave a triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. report that started with thanks to the people who helped clear more than 100 tickets from the milestone the previous Monday. By devchat time, there were just eight tickets in the milestone, and those were reported against trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision.. That is a stellar performance for this point in a release!

Also, huge thanks to @ryelle, who does a huge job producing the About page for every release — and has done so for the last four years that @marybaum is aware of.

5. Components and tickets

@webcommsat reported in for Help/About and Quick/Bulk Edit.

6. Open floor

@webcommsat also put out a call for contributors to help with end-user docs and training materials for 6.1 If you’re interested, contact the Docs and Training channels in SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.. They could use the help.

#core, #dev-chat, #summary