Dev Chat Summary: 05 June

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.

@desrosj facilitated a lively discussion with a number of contributors.

Announcements

@chanthaboune posted earlier today about new material to help Team Leads get going. If you’d like to get started leading WordPress teams, check out her material and feel free to ask questions or leave comments. The link is https://make.wordpress.org/updates/2019/06/03/team-lead-interest-post.

Upcoming Releases Discussion

Point releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality.

@audrasjb, co-lead of 5.2.2, outlined some points about the small number of tickets for the milestone. Since more than 60 tickets are committed in trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision./5.3, the release team suggested looking at landing some of those in the minor. The criteria, per the release handbook: tickets need to be self-contained and may not add new functions/files/filters to CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..

As a result, we have made some minor adjustments to the schedule:

Release Candidaterelease 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). 1: Monday, June 10, 2019, 8:00 PM GMT
Bug scrub: Thursday, June 06, 2019, 5:00 PM GMT
Release Candidate 2: Thursday, June 13, 2019, 5:00 PM GMT
Final Release: Tuesday, June 18, 2019, 5:00 PM GMT

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.

@desrosj reminded the group that @chanthaboune is still working on the logistics for the next major.

Got a ticketticket Created for both bug reports and feature development on the bug tracker. targeted for the milestone? Watching a few you’re really interested in? The team invites you to keep on scrubbing!

Call from Component Maintainers

Nothing major to say here

Open Floor

The theme review team is looking for a person with management skills to help accomplish goals and keep track of ongoing tasks.

If that interests you, please check this post out: https://make.wordpress.org/themes/2019/06/05/theme-review-team-meeting-agenda-for-11-june-2019

Some contributors asked for extra attention on these tickets:

testing of #40439 (@azaozz)
attention on #46289 and #33045 (@ramiy)
attention on #45202 (@afragen)

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