Dev Chat Agenda: January 30

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.

Below is the agenda for the weekly devchat meeting on Wednesday, January 30, 2019 at 21:00 UTC:

5.1 updates:
- Beta 3 delayed 24 hrs
- Schedule update.
- Field notes and dev notes status report.
Updates from focus leads and component maintainers.
WSOD protection
- the approach has altered following the raising of some security concerns
- the new approach is under development in #46130 after a discussion in the PHP channel
- discussion: the three options for the feature in WordPress 5.1 (please see the Make/core post delaying beta 3)
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 in the Making WordPress Slack.

#5-1, #agenda, #core, #dev-chat

Mike Schroder 6:56 pm on January 30, 2019

As part of the WSOD revert discussion, I’d like to discuss whether/how removing the WSOD protection from 5.1 affects the schedule for changing the PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher requirement for WordPress, since it will make it less safe for hosts to upgrade users’ sites before the requirement changes.

Comments are closed.

Welcome!

Communication

Share this: