4.9.8 Schedule

Note: This release was originally announced as 4.9.7.  Due to the 4.9.7 Security and Maintenance Release that rolled out on July 5, 2018 this release will now be 4.9.8.

The primary focuses of the 4.9.8 release are:

  • Introduce the Try Gutenberg callout ( #41316)
  • Privacy fixes/enhancements

The following is the current 4.9.8 release schedule:

Important Dates

  • Beta: July 17, 2018
  • RC: July 24, 2018
  • Release: July, 31 2018

Bug Scrubs

All bug scrubs will take place in #core.

#4-9-8, #bug-scrub

Core editor bug scrub time shift

With the shifts in local times, we’ll adjust the weekly core editor bug scrub starting this week to be Thursdays at 16:00 UTC and held as usual in #core-editor. Our focus will continue to be on Issues in the Merge Proposal milestone so please join the weekly discussion!

#bug-scrub, #core-editor, #gutenberg

Remaining Bug Scrubs for 4.9

The following bug scrubs have been planned for remainder of the 4.9 release cycle, focused on tickets remaining in the milestone, and will take place in #core:

As a refresher, here's a post from the 4.7 release cycle answering questions about bug scrubs.

#4-9, #bug-scrub

Bug Scrubs for 4.9 Beta 1

The following bug scrubs have been planned for the 4.9 release:

Reminder that Wednesday, October 4th is 4.9 Beta 1 and from that point on, no more commits for any new enhancements or feature requests will be allowed in this release cycle, only bug fixes and inline documentation. Work can continue on enhancements and feature requests not completed and committed by this point, but will not be picked up for commit again until the start of the next WordPress release cycle.

As a refresher, here’s a post from the 4.7 release cycle answering questions about bug scrubs.

#4-9, #bug-scrub

4.8.1 Bug Scrubs (part deux)

The following bug scrubs have been scheduled on tickets milestoned for 4.8.1 and the conversation will take place in #core:

Reminder of the timeline for 4.8.1 is Beta on Monday, July 17th (soft string freeze), RC on Monday, July 24th (hard string freeze), and launch on Tuesday, August 1st. In order to support that, we’ll be aiming for 0 tickets in the milestone by RC so we’ll be heavily focused on punting tickets out of the milestone.

#4-8-1, #bug-scrub

4.8.1 Bug Scrubs

The following bug scrubs have been scheduled on tickets milestoned for 4.8.1 and the conversation will take place in #core.:

Reminder of the tentative timeline for 4.8.1 is the last week of July so we’ll be heavily focused on punting tickets out of the milestone to ensure it’s clean ahead of the intended launch timeframe.

#4-8-1, #bug-scrub

Announcing a weekly new contributors meeting

As discussed at the last core dev chat, we will begin holding weekly meetings focused on new contributors to WordPress core, starting with our first meeting Wed July 5, 2017 at 19:00UTC (plus potentially alternate timeslots to accommodate contributors of all time zones, please comment below with a suggested UTC time).

The new contributors meeting is the perfect place to come if you are new to contributing to WordPress core and have questions!

@flixos90, @welcher, @stevenkword and @desrosj have all volunteered to rotate helping facilitate the meetings. We will:

  • Welcome new contributor questions, large and small.
  • Focus on assisting new contributors with tickets or patches.
  • Scrub the good-first-bugs report on trac.wordpress.org to ensure these tickets get attention.

We hope you will join us. What do you think? Any questions? Leave a comment below.

#new-contributors

4.8 Bug Scrubs for RC 1

The following bug scrubs will help us drop to 0 tickets in the 4.8 milestone by RC1 on Thursday, May 25th:

Reminder that Thursday, May 25th is 4.8 Release Candidate 1.

As a refresher, here’s a post from the 4.7 release cycle answering questions about bug scrubs.

#4-8, #bug-scrub

4.8 Bug Scrubs for Beta 1

The following bug scrubs have been planned for the 4.8 release:

Reminder that Friday, May 12th is 4.8 Beta 1 and from that point on, no more commits for any new enhancements or feature requests will be allowed in this release cycle, only bug fixes and inline documentation. Work can continue on enhancements and feature requests not completed and committed by this point, but will not be picked up for commit again until the start of the WordPress 4.9 release cycle.

As a refresher, here’s a post from the 4.7 release cycle answering questions about bug scrubs.

#4-8, #bug-scrub

4.7.4 Bug Scrub

Thursday, April 13th 15:00 UTC has been scheduled for a bug scrub.

The bug scrub focus will be on tickets milestoned for 4.7.4 and the conversation will take place in #core. This will be the final bug scrub for 4.7.4 and any tickets remaining in the milestone after the bug scrub will be punted to 4.7.5 or a future release. Reminder that 4.7.4 is scheduled for release on Tuesday, April 18, 2017 with Thursday, April 20, 2017 as a fallback.

#4-7-4, #bug-scrub