This post summarizes the weekly devchat meeting held Wednesday, July 18, 2018 (agenda | Slack archive). I updated the date!
The freshest of news from release leads @pbiron and @joshuawold, and deputies @sergeybiryukov and @psykro:
Beta 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. 1
- 4.9.8 Beta 1 was released Tuesday, July 17, 2018. It’s open for testing, so hop on these tickets.
- Beta 1 includes an updated version of TinyMCE (4.8.0). It needs special attention, since it was not thoroughly vetted before the release. Here are the release notes and change log, so go forth and test!
4.9.8 Beta 2
Note: 4.9.8 Beta 2 was released as planned in the notes below. I am a monster and very late with the dev chat recap.
- 4.9.8 Beta 2 release scheduled for Thursday, July 19, 2018, with the goal of including the Try Gutenberg 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/ callout. There are some issues on the callout that need attention, so it may be reverted if necessary.
- @kadamwhite back-ported r43510 for inclusion in Beta 2, as it may also help with Gutenberg meta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. handling. It’s quite the cohesive Beta 2 release, as Tim Gunn would say.
- Any other Beta 2 inclusions are listed here.
Focus Lead and Component Maintainer Updates
Two chat summaries for you to peruse:
Open Floor / Q&A
Question via @pbiron: If the privacy bug 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. fixes mentioned previously become ready, do we need to another beta for those or can they be included in
RC without appearing in a Beta?
The consensus is that it’s best to do a Beta release for privacy bug fixes. However, @desrosj is out until Monday, so including these fixes in a Beta this Tuesday and delaying RC 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). to Thursday/Friday is probably not doable. The current plan is to keep the schedule below, and reevaluate the significance of the open privacy bugs with @desrosj upon his return:
- Beta 2 – Thursday, July 19, 2018
- RC – Tuesday, July 24, 2018
- Final – Tuesday, July 31, 2018
Devchat Coordination Reminder
Jeff Paul is on vacation, so @whitneyyadrich, @audrasjb, @joemcgill, and @antpb are handling PM-y devchat duties this month: collecting agenda items, publishing an agenda, running the actual devchat meeting, and publishing a devchat summary.
The next meeting will take place on Wednesday, July 25, 2018, 20:00:00 UTC in the #core Slack 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 make the meeting, please leave a comment on this post so that we can take them into account.