Dev Chat Agenda: March 14th (4.9.5 week 6)

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.

Daniel James 7:54 am on March 14, 2018

I may not be around tonight for this dev chat but I’d like to bring up the discussion from last week around what features can possibly be included in the 4.9.5 release and what should be left out. Additionally, should the next major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope. be 4.10 and break tradition or go straight to 5.0 as originally planned.

Pinging @audrasjb & @sergeybiryukov so you know 🙂
- Jeffrey Paul 3:28 pm on March 14, 2018
  
  I figured we might get to those topics specifically, but that the important thing to cover was HOW we could land specific projects (GDPR, serve happy, debug screen, on-boarding improvements, 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/) between now and the intended release date for Gutenberg. If the solution happens to be expanding scope of minor releases, using a 4.10 release number, or something else that’s fine; but I wanted to focus more on the problem and less on individually discussing the solutions first.

Comments are closed.

Welcome!

Communication

Share this: