Dev Chat Summary: January 9

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.

Thanks for everyone that attended, you can catch the archive here.

5.0.3 updates

It’s out! Congrats @desrosj, @audrasjb and everyone.

5.1 updates

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 coming on Jan 10. Ticketticket Created for both bug reports and feature development on the bug tracker. list here to close or puntpunt Contributors sometimes use the verb "punt" when talking about a ticket. This means it is being pushed out to a future release. This typically occurs for lower priority tickets near the end of the release cycle that don't "make the cut." In this is colloquial usage of the word, it means to delay or equivocate. (It also describes a play in American football where a team essentially passes up on an opportunity, hoping to put themselves in a better position later to try again.) before then.
- Aiming for 2000-2200 UTC, give or take.
Help is needed right now for triaging that list. You can help get 5.1 to beta, a great start is by reviewing tickets here.
There has been a change with PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher-FPM detailed here. @pento made a request for hosts to test this change.
@matt is leading with @pento as deputy for this release.

Updates from focus leads and component maintainers

Editor

New release of GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/.
There is also some early discovery/ideation of phase 2 boundaries starting here.
Conversation on the design/research side here.

Media

Still working on identifying places to remove cruft and also some excellent work on clearing up tickets in preparation for 5.1.

JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors.

Planning for 2019 got started along with a discussion of auditing existing documentation for accuracy.

Open floor

Action requested on discussion of tackling lingering TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets. Please share your thoughts.
The bulk edit that happened last week, was not based on the proposal in the post by @desrosj.
The triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. team will be writing a post to start discussion of best practices soon and how to get involved.

#dev-chat #summary