Devchat summary: December 04, 2019

@francina led the chat based on this agenda.

Announcements

@audrasjb gave an update of 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 for 5.3.1 minor 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.. The current status is 3 scrubs already done and 3 others scheduled for the rest of the week. The agenda of the scrubs for the releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software. is available here. There are currently 20 tickets closed as fixed and 29 open for the milestone. Audras Jb also confirmed that targeted date for the release is December 11 or 12.

There was also a small discussion with @audrasjb, @marybaum, @azaozz and @johnbillion about the correct appellation of the testing phase before the minor release, either 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. of 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)..

@azaozz also stated that a good date for the first Release Candidate can be early in the week of Monday 9, and that the team can organize another scrubs if any new bugs appear.

@francina gathered opinions about the release team. The team for WordPress 5.3.1 release is officially constituted by @sergey, @audrasjb, @amy kamala, @marybaum, and @whyisjake.

@francina reminded about 5.4 release which is still  in early stages, and shared the link of its open call for tickets. Everyone interested is invited to add their comments.

Highlighted Blogblog (versus network, site) Posts

@francina shared this post about WordPress 5.3 retrospective recap and next steps.

Open Floor

Another discussion about a possible date for 5.4 and releases cycles duration happened. @francina reminded that the targeted date for now is March 31st 2020, after @jorbin asked if it can take place in January.

Francina also precised that there is currently an ongoing discussion about shortening the futures releases cycles.

@azaozz stated that “historically” the holiday season has been slow on the “development” side and quite lively on “organizational” side, and that this can be a good time to speed things up.

@jorbin stated that the short cycle for 5.1 last year showed that we can get a beta out in January and release in February without much difficulty.  @francina then point us to this Matt’s message, where he mentioned that the team is trying to get as much as possible into point releases, including possibly 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/ updates; point releases being only about regressions.

@jorbin reminded that during the 4.9 release cycle, the decision was made to start backporting some features. And that he thinks that this is only needed if we keep the slow major releases that we have had historically.

@francina then proposed a working group that will evaluate how we can reduce the manual work for the futures releases. And asked if there are already tools or procedures for that.

@johnbillion precised that his tought  is that a release schedule makes releases and makes time planning easier for everyone.

Important reminder from @nacin about the biggest focus area if the team want to speed up things should be automated testing and updates process.

The devchat hour ended up with @francina allowing attendees to continue the discussion for an extra time as it might be a kind of blockerblocker A bug which is so severe that it blocks a release. now.

The rest of the discussion about releases cycles can be found starting by here in #core.

Details about others aspects of this have been discussed in the following posts:

#devchat, #summary