Dev Chat Agenda for February 26, 2020 (5.4 Week 7)

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 the weekly meeting happening later today: Wednesday, February 26, 2020, at 09:00 PM UTC.

Announcements

This week marks week 6 of the 5.4 release cycle 🙌
WordPress 5.4 Beta 3 was released yesterday, February 25, as scheduled.

Highlighted Blogblog (versus network, site) Posts

Upcoming Releases – 5.4

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 to be released on March 3rd
5.4 and beyond: a discussion about the release cycle phases originated in the core-committers Slack channel.

Components Check-in

News from components
Components up for adoption (Filesystem API and Rewrite Rules)
Components that need help
Cross component collaboration

Open Floor

If you have anything to propose for the agenda or specific items related to those listed above, please leave a comment below.

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

#5-4, #agenda, #dev-chat

Francesca Marano 10:37 am on February 26, 2020

Bringing this over from last week 🙂

I would like to propose to change the Components Check-in. This is always done towards the end of the chat and feels rushed. There is never really time to dig into the topics they might bring up.
So I have two proposals:
1. Schedule a weekly post where they can leave their status update, like the one for Community deputies – it seems to be quite buggy lately and has to be scheduled manually instead of being “automagically” published 🙂
2. Adopt a SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. Bot that once a week will ask the maintainers for a status update: maybe in a new #compontent-maintainers Slack channel. CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. is getting very busy with TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. and Travis bots, and RSS.

Thank you for your consideration!

Comments are closed.