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

4.8 Bug Scrubs for RC 1

The following 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 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 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 have been planned for the 4.8 release:

Reminder that Friday, May 12th is 4.8 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. 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 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 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

Weekly Multisite Bug Scrubs

The multisitemultisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site team has recently been focussed on figuring out and planning the implementation of REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/. support for multisite features, which has been the primary topic during the weekly office hours. Unfortunately discussion about regular bugs and small enhancements has been a bit on hold because of that.

Therefore we would like to start running weekly 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 again, and in Tuesday’s meeting we decided to have these every Monday at 18:00 UTC. We will continue to primarily focus on the REST API during office hours, so there will be a clear separation of concerns.

Please join us in #core-multisite if you’re interested or have a bug to discuss. The initial bug scrub will be on Monday 18:00 UTC.

#bug-scrub, #multisite, #networks-sites

4.7.1 Bug Scrub

Thursday, January 5th 12:30pm CST has been scheduled for a bug scrub.

The 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 focus will be on tickets milestoned for 4.7.1 and the conversation will take place in #core. This will be the final bug scrub for 4.7.1 and any tickets remaining in the milestone after the bug scrub will be punted to 4.7.2 or a future release. Reminder that 4.7.1 is scheduled for release on Tuesday, January 10, 2017.

#4-7-1, #bug-scrub

Bug Scrubs for week of December 5th

The following times have been scheduled for bug scrubs this week:

Thursday, December 8th 10:00am CST. Focus will be on tickets milestoned for 4.7.1 and the conversation will take place in #core.

Friday, December 9th 20:00 UTC. Focus will be on Customize tickets milestoned for 4.7.1 and the conversation will take place in #core-customize.

 

#4-7-1, #bug-scrub

Bug Scrubs for week of November 7th (4.7 week 12)

The following times have been scheduled for bug scrubs this week in #core:

Tuesday, November 8th 2:00pm EST. Focus will be on tickets remaining in the milestone.

Wednesday, November 9th 10:00am EST. Focus will be on tickets remaining in the milestone.

Wednesday, November 9th 2:00pm EST. Focus will be on tickets remaining in the milestone.

 

Note that Wednesday is the planned release for Beta 3.

#4-7, #bug-scrub

Bug Scrubs for week of October 24th (4.7 week 9)

The following times have been scheduled for bug scrubs this week in #core:

Monday, October 24th 3:00pm CDT for 3 hours. Focus will be on milestoned feature requests and enhancements. Any that remain without a close or commit keyword will be punted on Tuesday; if a committercommitter A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component. wants to bring it back before the deadline they can.

Wednesday, October 26th 9:00am CDT for 2.5 hours. Focus will be ensuring the milestoned feature requests and enhancements are clear and then move on to the milestoned defects and tasks. This is the deadline for feature requests and enhancements to make it into 4.7.

Thursday, October 27th 9:00am CDT for 2.5 hours. Focus will be on milestoned defects and tasks.

Friday, October 28th 9:00am CDT for 2.5 hours. Focus will be on milestoned defects and tasks and generally all that remains in the milestone.

#4-7, #bug-scrub

Docs-focused Bug Scrub Friday

We’ll have a docs-focused 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 Friday, Oct. 7 2016 14:00 CDT in the #docs 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, for anyone interested in contributing. We’ll focus on the `needs-docs` keyword first, then on the `docs` focus if there’s time.

#4-7, #bug-scrub, #inline-docs