Dev Chat Summary: May 24th (4.8 week 4)

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.

This post summarizes the dev chat meeting from May 24th (agenda, Slack archive).

4.8 Timing

Beta 1 went out on Friday, May 12th; Beta 2 went out on Monday, May 22nd
RC1 is scheduled for Thursday, May 25th
With RC1 we’re aiming for a soft string freeze so that translators can work through all the new strings in 4.8
Should things continue to go to plan, RC2 would be next Thursday, June 1st

4.8 Bug Scrubs

Currently at 6 tickets in the milestone, goal is to get to 0 by RC1
Daily scrubs planned until RC1, highfives to @flixos90 @obenland @desrosj for helping on this!

4.8 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. / 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.

Goal is to have Dev Notes all done ASAP so we can assemble the Field Guide by RC1
Remaining Dev Notes to get published:
- 1) Editor: Edge fixes – @iseulde & @azaozz
- 2) Media Widgets – @westonruter
- 3) Tag Cloud widgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. – @afercia
Listing of all tickets tagged with needs-dev-note

About Page

#40721: dev help needed writing copy for the Under the Hood section, please pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” @melchoyce if you can help

#4-8, #core, #dev-chat, #summary

Welcome!

Communication

4.8 Timing

4.8 Bug Scrubs

About Page

Share this: