Dev Chat Summary: July 4th (4.9.8 week 1) [updated]

Please note: the previously scheduled 4.9.7 is now referred to as 4.9.8, since 4.9.7 has been released by the security team.

This post summarizes the dev chat meeting from July 4th (agendaSlack archive).

@joemcgill @audrasjb, @antpb, and @Whitney are helping out with dev chats coordination while @jeffpaul is on holiday.

4.9.8 Details

@pbiron and @joshuawold will be serving as 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. leads during this cycle, with @sergey and @psykro handling deputy duties.

4.9.8 Release Main Schedule:

  • 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.: July 17, 2018
  • RC: July 24, 2018
  • Final Release: July 31, 2018

The schedule for the 4.9.8 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 will be:

  • Thursdays at 21:30 UTC
  • Mondays at 14;00 UTC

The hope is that with those two different times a good majority of interested parties will be able to join one or the other.

4.9.8 Main Focus:

  • Introduction of the Try Gutenberg callout #41316
  • Privacy fixes/enhancements

Of course, 4.9.8 won’t be limited to those, but they will be the primaries.

Updates from focus leads and component maintainers

  • The JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/. team published notes from their meeting where they discussed deprecation strategy, sunsetting the packages repository, coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. CSSCSS Cascading Style Sheets., code style, and some developer setup tickets.
    https://make.wordpress.org/core/2018/07/04/javascript-chat-summary-july-3rd/
  • The PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 team also posted notes from their meeting this week
    https://make.wordpress.org/core/2018/07/02/php-meeting-recap-june-25th/

Thanks to both teams for posting notes from their chats. Reminder to focus leads and component maintainers to try and publish meeting notes from your chats to help socialize what’s happening across the different parts here in WordPress Core.

Open floor

  • @davecpage brought ticketticket Created for both bug reports and feature development on the bug tracker. #38280 to find out if it’s possible to get into 4.9.8.
    This ticket needs a validation by a component maintainer to be included in the milestone, for example @boonebgorges.

Next meeting

The next meeting will take place on July 11, 2018 at 20:00 UTC in the #core SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel. Please feel free to drop in with any updates or questions. If you have items to discuss but cannot makemake A collection of P2 blogs at make.wordpress.org, which are the home to a number of contributor groups, including core development (make/core, formerly "wpdevel"), the UI working group (make/ui), translators (make/polyglots), the theme reviewers (make/themes), resources for plugin authors (make/plugins), and the accessibility working group (make/accessibility). the meeting, please leave a comment on this post so that we can take them into account.