The facilitator for this week’s chat was @audrasjb.
Announcements
WordPress version 5.3-RC2 was released on Tuesday. Everyone please help by testing out the 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)..
The latest Dev 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. published for 5.3 discuses “Noteworthy Admin (and super admin) CSS Cascading Style Sheets. Changes in WordPress 5.3”.
Also, the official Field Guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page. for 5.3 was published!
@audrasjb called attention to the wonderful documentation work this cycle by @justinahinon and @jeffpaul. Thank you to both for their extraordinary efforts!
5.3 Updates
@azaozz Pointed out that there are only two tickets needing work after RC2, excluding the About Page. Follow the ticket Created for both bug reports and feature development on the bug tracker. progress in Trac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. here.
@ianbelanger informed the group that there are currently 0 tickets in the Bundled Themes component for Twenty Twenty. However, he added that an RC3 release would be helpful.
@audrasjb brought up ticket #48396 regarding @afercia‘s request to revert two lines of CSS to remove an unwanted changes on disabled buttons. @azaozz confirmed the revert to be a minor one and suggested that it move forward based on testing.
A pre-RC3 Bug Scrub in the #core channel was tentatively scheduled for Monday October 28, 2019 15:00 UTC. If there are no new tickets or regressions reported prior, the scrub will not take place.
@sergeybiryukov asked about branching for 5.3 this week. @peterwilsoncc suggested certainly branching before WordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. US Contributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/., as to allow for good-first-tickets to be committed for new contributors. @desrosj added that branching could be done at any time now that the dust has settled from RC2, but deferred to @azaozz‘s judgement as Core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Tech Lead for 5.3. @azaozz suggested trying to resolve a couple of remaining issues in 5.3 prior to branching in the next few days, and a consensus was reached around this idea.
These notes were taking by @davidbaumwald and proofread by @audrasjb
#5-3, #dev-chat, #summary
