Link to the start of the meeting in the WordPress Core Slack
Agenda
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 and @webcommsat led the meeting.
Announcements
WordPress 5.9 Release Candidate 3 is available.
Two key resources:
Help test WordPress 5.9 features
Read the 5.9 Field Guide.
Blog (versus network, site) posts of note
Update on the release
@hellofromtonya
5.9 final will land next week on 25 Jan 2022. RC3 yesterday was the last planned release before the final. If blockers or regressions are reported before 5.9 starts its 24 hour code freeze (which starts on 24 Jan), then another 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). may happen. As of right now, there are not any reports that warrant another RC. But will keep on on it.
@jeffpaul: You’re almost there @hellofromtonya, we’re all in support of you and the team, thanks again for everyone’s amazing work!
Release Process summary from @hellofromtonya
- The release squad is discussing the start time for the release party on the 25th. Stay tuned.
- The code freeze will start exactly 24 hours before that time.
- Dry run will be on the 24th and end before that code freeze starts.
- A post on Make Core will appear in advance to outline the release processes and how you can help.
Thank you to all contributors who made this happen!
How can you help?
- Test
- Triage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. any reports that come into Trac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. or 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/ to help teams figure out if a report needs immediate attention. Then come join the 5.9 Release Party to help prep and test the package and get it out into the world! Celebrate.
- @webcommsat: please share the posts about the release and the RC3 post.
5.9.1 early discussions
@jeffpaul: wait until we see how the forum responses come in post 5.9 since it sounds like nothing needing another RC as of now.
@marybaum shared she and @estelaris would be helping with the release-coordination for the minors, in in the interregnum before 6.0.
@hellofromtonya: I agree with @jeffpaul and points @desroj raised in the release leads channel. Though there are fixes ready for 5.9.1, good to give a week or so for reports to come in within the forums, Gutenberg 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/, and Trac. Why? There may be things hadn’t yet surfaced that need priority attention.
@costdev: For reporting issues when testing RC, reproducing reported issues during/triage, and for when reports land in the forums and make their way to Trac, a test report template is available to help narrow down the steps and environments where issues may occur.
Open Floor
a) Request for core agenda to be published 24 hours ahead of a meeting to allow items and links o be more easily added for the discussion. It has not been published this far in advance in the last two weeks. Confirmed.
b) FSE
@annezazu: Join me for a hallway hangout on Thursday 20 January 2022 at 9:00pm UTC to talk about 5.9. It will be held in #fse-outreach-experiment and is meant to be a casual place to chat with other folks in the WordPress space. Bring your questions, pop in and out, etc. It will be recorded and recapped. Previous editions
c) Ticket Created for both bug reports and feature development on the bug tracker. #54859: New Welcome’s panel “Edit styles” link does not seem to work
@audrasjb: relating to 5.9: should we consider #54859 as a blocker A bug which is so severe that it blocks a release.? any thought about this small (but annoying) issue? Can probably be skipped to a minor unless there is a RC4.
@hellofromtonya: That issue needs testing and more discussion to determine what should happen and if reproducible. But does not seem to be a blocker for the 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..
If it’s merely a bad link, that’s one thing and easily fixable. If it’s something else, then discussion needs to happen about resolution.
@audrasjb: The expected behavior would be to open the Global Styles panel.
For now, the two links in the welcome panel both lead to the same screen (*), which is, indeed, annoying.
(* on 5.9 + TT2)
ironprogrammer: The first time you open Styles, it has the nifty tutorial, so it’s a shame to miss that when you come here the first time…
@hellofromtonya: The question is: What should the link be to open the panel (this would be fixable in Core)? Or is the panel not wired to a link (this would be a Gutenberg issue)?
@audrasjb: I don’t think it’s a blocker. But I think it’s annoying and it’s not a super user experience when associated to the Welcome panel which is supposed to show all the amazing stuff we shipped in this release. What I try to say is that it’s more a “communication issue” than a technical one. @jeffpaul agreed not a blocker.
@hellofromtonya:
- let’s get it fixed.
- Then if there are other issues that pop, it can be bundled into a RC4.
- I agree it has to be fixed upstream in Gutenberg and then packages released and backported to Core.
@hellofromtonya: Depends upon if the URL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org is correct or not. If not correct, then it can be fixed in Core. Else, yes, I agree it has to be fixed upstream in Gutenberg and then packages released and backported to Core.
@audrasjb: I’m currently opening an issue upstream, and also, I’m searching for any Gutenberg behavior that would open the panel based on the URL hash.
@audrasjb: If so, we could fix this on Core side.
@desrosj: I think we should be worried about making the right decisions for our users and not to avoid publications writing unfavorable pieces about us.
@marybaum: A thing that seems like not-a-blocker to us can affect UX User experience profoundly, which in turn can damage perception.
@hellofromtonya: For now, it’s prioritized and in the 5.9 milestone. I’ll take ownership of this issue with priority to fix it. Once fixed, then a decision can be made as to whether to do another RC or release it in.
@hellofromtonya: There are known bugs that do impact UX that are in 5.9.1. Yes, the release seeks to ship a solid experience. And yes, it would be great to have a perfect UX across the board. In this case, the link does take the user to the Site Editor where the Styles can be opened with another click. The experience is not broken nor perfect. But I don’t see it as a major blocker to the final release. But let’s see if it can be fixed quickly and if other issues come in to warrant another RC.
@audrasjb pinged the editor team
An issue has been reported that is a good to get fixed in case there’s a 5.9 RC4.
Clicking wp-admin/site-editor.php?styles=open in the Welcome panel is expected to automatically open the Styles panel in the Site Editor. It is not. Is this the right link? Or is this a 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. that needs to be fixed? https://github.com/WordPress/gutenberg/issues/38090
https://core.trac.wordpress.org/ticket/54859Posted in core-editor
d) 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.
@webcommsat and @courane01: For the work on Learn WordPress and social media, are there more dev notes on the release to come? Working on social media for LearnWP.
@marybaum: it looks like one more – https://github.com/orgs/WordPress/projects/11/views/8
Props: Meeting notes summary by: @webcommsat and light editing by @marybaum
#5-9, #dev-chat, #summary
