Dev Chat Agenda: September 2nd 2020

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 meetings happening at:
Wednesday September 2nd 05:00 UTC and Wednesday September 2nd 20:00 UTC.

Please share any items you’d like to include in the comments below.

Announcements
Highlighted blogblog (versus network, site) posts

Deprecated JS globals – No action required, posting for awareness
5.5.1 – No action required, posting for awareness
Core Chat – Timezones and Daylight savings – Request for comments please
Bug Scrub Schedule No Action required: Posted for awareness

Calls from component maintainers
Open Floor

If you have something else you want to include to the agenda, please mention it in the comments below.

The #dev-chat meetings will be held on Wednesday September 2nd 05:00 UTC and Wednesday September 2nd20:00 UTC These meetings are held in the #core channel. To join the meeting, you’ll need an account on the Making WordPress Slack.

#5-6, #agenda, #dev-chat

Dean 12:16 am on September 2, 2020

https://core.trac.wordpress.org/ticket/50630
- Dee Teal 2:07 am on September 2, 2020
  
  Hi Dean, can you give us a bit more context for adding this to the discussion in dev chat? It would be super helpful to have a bit more of a sense of what needs discussion and/or what outcomes you’re after. Thanks.
  - Dean 2:38 am on September 2, 2020
    
    Hi Dee, mostly I’m looking to have that 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./patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. triaged since there’s been no response for 8 weeks. If that’s something that’ll get done as part of the upcoming 5.6 bug triaging then no worries, but I will be available for the chat today in case there’s anything I can do to help move it along (more thinking in the open floor part). Thanks 🙂
Jake Spurlock 5:08 pm on September 2, 2020

With 5.5 released, I’d like to put together a retrospective on the release process. I’m working on the details right now, but as a first step, I’d like to catalog some responses on what went wrong, what went well, and what could be improved.

I’ll try to get this into a p2, but probably won’t be able to get that done ahead of the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. chat today.

Comments are closed.

Welcome!

Communication

Share this: