Dev Chat Summary: April 10


Five days left to submit a talk for WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. US at WordCamp US 2019

5.2 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. 3 is Thursday, April 11th; target release is April 30, so focus is on final pushes.

Bug Scrubs

There are two planned 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. scrubs prior to RC1. Check the post here for the schedule.

Dev Notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase.

Deadline for dev notes is this Friday, April 12.

Two were published on Make/Core; two more went up to Make/Themes but consensus was to move to Make/Core after some discussion. Three to four more are in the pipeline for Friday. A post on the new Site Health tool from @clorith will also get the dev-notes tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.).

@earnjam noted the choices for what needs notes are coming from this Trac list and this Gutenberg list.

All 5.2 dev notes will go in the Field GuideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page., which will go live with the 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). on April 17.

@jeffpaul has volunteered to help with the Field Guide.

Per the notes @williampatton wrote for Make/Themes: @chanthaboune clarified that she thought the best plan was to move all dev notes to Make/CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. to keep them all together and ensure broader reach.

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.

Deadline for Gutenberg changes to make 5.2 is also Friday, April 12. This is limited to bug fixes only.

Open Floor

Visibility of Dev Notes

@xkon started a discussion on the best way to surface dev notes for easiest access. He and other folks are now looking for All The Links and will comment on this post with their findings.

From there we’ll revisit the issue and use it to inform any changes to Make/Core and what we put on a proposed Core Contributor Handbook page.

WP Translationtranslation The process (or result) of changing text, words, and display formatting to support another language. Also see localization, internationalization. Day

@jeffpaul noted we’re just about a month out from WP Translation Day on May 11.


@milana_cap put out a request for someone to lead the Core PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher team at WCEU Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of There are many teams that people can participate in, each with a different focus.

Important dates

@chanthaboune closed with a list:

  • April 11 – WordPress 5.2 Beta 3 + soft string freeze
  • April 12 – Dev notes deadline
  • April 15 – WCUS Speaker application deadline
  • April 15 – Gutenberg 5.5 RC
  • April 17 – Gutenberg 5.5 Final
  • April 17 – WordPress 5.2 RC1 + hard string freeze (edited)

Props to @marybaum for writing this summary.

#5-2, #dev-chat, #summary