Dev Chat summary, February 2, 2022

Link to the start of the meeting in the Make WordPress core Slack channel

Agenda for the WordPress developers chat meeting, held weekly in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..

Announcements

a) WordPress 5.9 retrospective (please leave your comments by February 14, 2022)
b) Proposal: 2022 major release timings (January 27, 2022)
c) Redesign of wordpress.org/news is coming
https://twitter.com/WordPress/status/1487805666093940744
Redesign first shared in the Design Team blog post (June 2021).
@estelaris: More info in the Figma about the colors.

The meeting had a limited discussion on the whether there was a new palette/ brand colors.

WordPress 5.9.1

Tickets

@audrasjb: update on tickets in milestone 5.9.1

  • 34 open tickets for now (and probably more in the awaiting review queue), so we’re probably going to have a quick point releaseMinor 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.
  • after dev chat, 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. scrub was run focusing on moving GutenbergGutenberg 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/ related tickets to GitHubGitHub GitHub is a website that offers online implementation of git repositories that can 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/. Start of the bug scrub in Slack. 
  • it looks like Twenty Twenty Two theme will need an update in 5.9.1

Contributors/ volunteer for Editor tech lead needed

  • Still time for people to volunteer. Open to new people.
  • Core tech: @audrasjb willing to stand, but he also welcomed other volunteers
  • Editor tech lead: needed urgently. This would be a 5.9.x co-lead from the editor/Gutenberg side of things.
  • @desrosj: It may make sense to have two technical coordinators, at least for 5.9.1 (one core, one Gutenberg). Since this release is going to go out relatively quickly, it will help to have one person on each side that deeply understand the moving parts. But would help to have others around to help with the communication tasks.
  • Co-ordinators for minors to include: @marybaum

Discussions around proposed timing for next minor releaseMinor 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.

  • @jeffpaul: timeline would depend a bit on the core/editor leads it seems
  • @desrosj shared his learning from others: as much as possible, final releases should happen on Tuesday or Wednesday. Thursday releases come out on Friday for some folks. So unless there’s no other option (like with a security vulnerability disclosure date, or something of that nature), Tuesday and Wednesday are preferred. Thursday releases ok for Release Candidates for minor releases.
  • @audrasjb: We have a lot of 5.9.1 TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets. Many of them need to be reported upstream on GitHub Then we need to coordinate with #core-editor team to define a scope and a planning.
  • Suggestion after discussion: Release Candidaterelease 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). (RCrelease 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).) next Wednesday (9 February 2022) and one week after for final release as a goal.

GitHub processes

Update shared by @jeffpaul and @desrosj: The Ensuring Proper Attribution for Contributions to WordPress on GitHub proposal is temporarily withdrawn while specifics in the analysis and recommendation are updated. Please continue to read the post and comment directly on it with any additional input while a more precise proposal is updated and presented.

Component maintainers

@webcommsat: maintainers working through tickets on quick/bulk edit component. Question: is if ok to start holding scrubs for the component now that 5.9 is released as some tickets would benefit from a discussion in core?

Answers from the floor which are useful for other component maintainers and those getting involved in bug scrubs:

  • you can hold scrubs on any component whenever you choose as it is helpful to continue on Trac to keep things moving along
  • @desrosj: component maintainers are free to hold scrubs whenever they feel is appropriate
  • But the tickets may not get committed and closed if it’s too close to a release. So just choose a good ticketticket Created for both bug reports and feature development on the bug tracker. report to scrub.
  • Tutorials for leading bug scrubs. Any unanswered questions can be added.
  • @marybaum: fixed bugs can go into a minor release — but not features or enhancements
  • @jeffpaul: releasing minor versions handbook page

Next meeting

The next dev chat meeting: 9 February 2022, at 20:00 UTC. An agenda is aimed to be published on the Core blogblog (versus network, site) 24 hours before the meeting. Additional items and links to particular core posts are invited on agenda posts through the comments section.

If you would be interested in writing dev chat summary, contact Core team reps @marybaum and @audrasjb, or put yourself forward in the weekly meeting.

Props to: @webcommsat for pulling together information for the agenda and the notes, to @marybaum for leading the meeting, and to @audrasjb for reviewing the notes.

#5-9-1, #dev-chat, #summary