The meetings take place on Wednesdays at 20:00 UTC in the #core channel on Slack, and usually last an hour. All are welcome to attend or catch up via the summary.
About Dev Chat.
The publication of the Dev Chat agenda was held for the release party of WordPress 6.1to include the updates related to it.
1. Welcome
Introduction from core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. 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
Dev Chat summary, October 27, 2022 – thanks to @webcommsat for writing it and for checking items for today’s agenda.
2. Announcements
WordPress 6.1 “Misha” was released, November 1, 2022
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/ 14.5 RC 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). expected November 2, 2022
During the last week:
6.1 Release Candidate 6 – October 31, 2022
6.1 Release Candidate 5 – October 28, 2022
Gutenberg 14.4 was released –“What’s new in Gutenberg 14.4” release post, October 27, 2022.
3. Blog (versus network, site) posts of note
A Week in Core – October 31, 2022
Performance chat summary, November 1, 2022 – has some ticket Created for both bug reports and feature development on the bug tracker. updates including WebP, AVIF images, Object Cache. Also some calls for reviews.
Core editor improvement: enhancing the writing experience, October 28, 2022. Find more about other improvements to the core editor.
4. Forthcoming releases
Updates from the relevant teams relating to releases.
a) Latest 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.1
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. for 6.1 find them at the dev-notes-6-1 tag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.). The Field Guide for 6.1.
b) Next minor 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.: 6.1.1
c) Next major: 6.2
Is there an update on the discussion on earlies?
If you have an update from release leads or any teams collaborating on related items, please add a comment.
5. Component maintainers updates / tickets / requests for help
Please add your request for tickets you would like to raise as a comment.
6. Open Floor
Please add your Open Floor item as a comment.
Thanks to @marybaum for reviewing the agenda.
#6-1, #agenda, #dev-chat
#6-1, #6-1-1, #6-2, #agenda, #dev-chat
