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

4.9.5 feedback

• @audrasjb wrapping up feedback post, aiming to publish by end of week on experience leading 4.9.5
• No other feedback, so no urgent need to rush out immediate fixes in 4.9.6

4.9.6 planning

• @desrosj self-nominated to be co-lead, @melchoyce nominated @allendav to be co-lead, @sergey self-nominated to be a deputy (given desire to have a lead with commit access); all have accepted and will begin planning, many thanks to them!
• @desrosj to focus on coordinating release, @allendav to focus on GDPR, @sergey to focus on review and commits were needed
• Will want to line up someone to help with packaging ~48 hours ahead of 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., RCrelease 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)., and release
• Tentative timeline: beta on Tuesday, April 24th, RC on Tuesday, May 1st, and Release on Tuesday, May 8th (will be confirmed in next week’s devchat)
• Planning to begin communicating via Make/CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. of what’s going into 4.9.6 and will encourage devs to utilize 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.
• @desrosj and @jbpaul17 to work on 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. scrub schedule

Updates from focus leads and component maintainers

• The Editor / 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/ team is canceling their weekly bug scrubs that had been occurring on Thursdays. They also released v2.6 with a detailed write-up on the changes.
• The GDPR Compliance team shared an update on opt-in commenter cookies as well as notes from their previous meeting.
• @miss_jwo reminded everyone about the Community Code of Conduct survey closes tomorrow (direct survey link)

Next meeting

The next meeting will take place on April 18, 2018 at 20:00 UTC / April 18, 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 make the meeting, please leave a comment on this post so that we can take them into account.

#4-9-6, #core, #dev-chat, #summary