Dev Chat Agenda for May 5, 2021

Welcome!

The WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:

Found 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.? Create a ticket in the bug tracker.

Want to contribute? Get started quickly with tickets marked as good first bugs for new contributors or join a bug scrub. There’s more on the reports page, like patches needing testing, and on feature projects page.

Other questions? Here is a detailed handbook for contributors, complete with tutorials.

Here is the agenda for this week’s developer meetings to occur at the following times: May 5, 2021 at 5:00 UTC and May 5, 2021 at 20:00 UTC.

Blogblog (versus network, site) Post Highlights

A Week in Core – May 3, 2021
Expired GitHub and WordPress.org profile connections
Docs Focus role & workflow during WordPress release cycle
Full Site Editing Go/No Go: Next steps (outlines blockBlock 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. editor work remaining for 5.8 release)

Blog posts that need feedback

Proposal: new workflow keyword to exclude tickets until review is needed

5.8 Schedule Review

Bug Scrub schedule (TBD via @lukecarbis and @boniu91)
Marketing schedule (based on earlier plans)
Feature Freeze in 20 days on Tuesday, May 25th
BetaBeta 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 in 34 days on Tuesday, June 8th
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). 1 in 55 days on Tuesday, June 29th
5.8 release in 76 days on Tuesday, July 20th

Components check-in and status updates

5.8 plans and help needed
Check-in with each component for status updates.
Poll for components that need assistance.

Open Floor

Do you have something to propose for the agenda, or a specific item relevant to the usual agenda items above?

Please leave a comment, and say whether or not you’ll be in the chat, so the group can either give you the floor or bring up your topic for you accordingly.

This meeting happens in the #core channel. To join the meeting, you’ll need an account on the Making WordPress Slack.

Props @desrosj for peer review.

#5-8, #agenda, #dev-chat

Jeffrey Paul 1:55 am on May 5, 2021

I’d also like to add the recently published WordPress 5.8: What’s on your to-do list? post to the “Blogblog (versus network, site) posts that need feedback” list to ensure @desrosj and I have the input we need to help shepherd the necessary work in the 5.8 release cycle.
Paul Biron 2:15 am on May 5, 2021

Another blogblog (versus network, site) post to highlight is [Feature project] Updates on updating the updaters

Comments are closed.