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 beta, RC, 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/Core of what’s going into 4.9.6 and will encourage devs to utilize trunk
-
@desrosj and @jbpaul17 to work on bug scrub schedule
Updates from focus leads and component maintainers
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 Slack 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-5, #4-9-6, #code-of-conduct, #core, #core-editor, #dev-chat, #gdpr-compliance, #gutenberg, #summary