(Update March 11, 2022: 6.0 Planning Update )
Start of the meeting on the Make WordPress Core Core is the set of software required to run WordPress. The Core Development Team builds 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/. channel.
Dev Chat agenda, March 9, 2022
Dev Chat summary, March 2, 2023
1. Announcements
The Performance Team has released its first plugin!
2. Blog (versus network, site) posts of note
- From @audrasjb: A Week in Core, March 7, 2022
- From @annezazu: A Core Editor Improvement: Choose your Style
- From 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/ Times: Introducing the Museum of Block Art
- Really helpful series on improvements to the core editor thanks to @annezazu and others. Choose your style. This is part of a series dedicated to highlighting new features, improvements, and more to discover the various Core Editor related projects. Just click on the 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.) #core-editor-improvement tag in the Make WordPress core blog to keep up-to-date on this.
3. Upcoming releases
a) 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
A great source of information about the next release is the 6.0 release development cycle section on the Make WordPress core.
Release co-ordinators: @annezazu has agreed to be a co-release coordinator this week alongside @priethor.
Progress for 6.0: the biggest pieces are moving along for the core editor including Styles engine, pattern integration, improvements to block Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. theme creation process, and improvements in the works for switching to block themes.
Editor Tech Lead: @jeffpaul: any traction on confirming the Editor Tech Lead? @annezazu advised the core editor tech lead is known and in progress of being resolved. She will update in dev chat and agreed it is critical to have this role in place.
Bug scrubs for 6.0
- Five weeks out from 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. 1, query on 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. scrubs. Suggestion to add a bug scrub schedule to the 6.0 development cycle page when it is available. @annezazu to follow up on what is missing on bug scrubs.
- Update post dev chat: @costdev is joining as a co-Triage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. lead. The change has been updated on the release page. It allows us to have great timezone coverage for the squad in a very important role. Next step: to get a bug scrub schedule in place (more context).
@webcommsat: On March 14, 2022, at 20:00 UTC, bug scrubs on the About Page and Quick/ Bulk Edit components will begin. Requested to @marybaumand @audrasjb for these to be added to the bug scrub schedule.
b) 5.9.2 Next Maintenance Release Update:
- Trac tickets (1 already backported and 4 ready for backport A port is when code from one branch (or trunk) is merged into another branch or trunk. Some changes in WordPress point releases are the result of backporting code from trunk to the release branch., on 22 tickets)
- 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/ issues (22 fixed, on 69 issues): https://github.com/WordPress/gutenberg/projects/63
@audrasjb and @mamaduka will publish a release schedule on Make/Core for the next maintenance release in the next couple of days.
c) Gutenberg
Released Gutenberg 12.8 RC1 in the #core-editor channel.
4. Open Floor
Tickets/ PRs
- @clorith asked if there was an editor lead for 5.9.2? @annezazu will try to follow up.
- Discussion on @clorith 5.9 regression ticket with some potential solutions (Gutenberg issue 39155). @audrasjb: moved it to 5.9.x todo.
- @afragen: discussion re: plugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party dependencies in the issues https://github.com/WordPress/wp-plugin-dependencies/issues/ Mostly around architecture and design initially.
- Highlighting PRs from @getdave for anyone who enjoys exploring things early – Slack link.
Two interesting PRs on the Navigation Menus system to allow menus to be manipulated in isolation from the Navigation block: Dedicated Navigation sidebar.
- Request from @craigfrancis on Trac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets #52506 and #54042 to get them ready for 6.0, and thanks to @peterwilsoncc for some tweaks on the former
- Request for anyone able to also test the patch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. in Trac ticket 42916 ahead of bug scrub on Monday on Quick Edit.
Gutenberg updates in dev chat
- @webcommsat: Request to be able to better highlight Gutenberg updates in dev chat in the blog posts or release sections of the meeting? @annezazu: to think through if there could be an async update to share to tie in with the 6.0 update.
Update post dev chat on March 10, 2022:
Light Process for 6.0 Updates for Core Dev Meetings
@annezazu chatted with @priethor and @peterwilsoncc about how best to handle updates for 6.0, partially due to timezone spread. To make things easier, we are going to embrace async updates for the win that can then be shared in the meeting. This matches an approach the Core Editor meeting has taken for project updates. As a result, expect the following:
- An async thread started each Tuesday (a day before core dev meetings) where release leads can share their updates at some point before the core dev meeting. @annezazu and @priethor will expect to usually hear from the Core Tech, Core Editor Tech and release coordinator leads but all are welcome to share anything relevant. For core editor, aim to summarize what’s shared earlier in the day for the core editor meeting (example).
- From there, those updates can be re-shared by @marybaum /@webcommsat during meetings.
Volunteer for dev chat notes
If you could volunteer for dev chat summary in the future, reach out to @marybaum and @audrasjb, the Core Team Reps. It’s a great way to keep up with all the moving parts of a release, and with the things that happen in between!
Props to: @marybaum for the agenda and leading the meeting, and to @webcommsat for co-facilitating and the dev chat summary. Thanks for review by: @marybaum and @annezazu.
#5-9-2-2, #6-0, #dev-chat, #summary
