Bug Scrub Changes and Recap of 2/12/2016 Bug Scrub

As announced previously, for the next two weeks only, bug scrubs will be held daily Tuesday, February 16th 17:00 UTC to Friday, February 19th 17:00 UTC and  Monday, February 22nd 17:00 UTC to Friday, February 26th 17:00 UTC. These bugscrubs will only focus on tickets that are milestoned for 4.5 inclusion, in order to reduce the number of tickets open in the milestone before the enhancement merge window closes Wednesday, February 24th 17:00 UTC.

On Friday, February 12th at 17:00 UTC, we had our regularly scheduled bug scrub. As a reminder, for the 4.5 release, trac bug scrubs will be held normally weekly each Friday at 17:00 UTC. Bug scrubs are held in the #core channel of WordPress Slack.

The Slack archive for last week’s meeting begins here: https://wordpress.slack.com/archives/core/p1455296539002539

During the bug scrub, the following tickets were covered:

#35495, #22363, #24251, #35807, #34625, #12955, #21667, #35774, #35804, #35720, #35716, #35422, #35427, #35428, #34913, #20537, #18997, #32075, #35160, #31237, #35390

We’ll return to the standard pre-submitted & open floor format after two weeks.

#bug-scrub, #trac-cleanup

Call for Trac Tickets and Recap of 2/5/2016 Bug Scrub

On Friday, February 5th at 17:00 UTC, we had our regularly scheduled bug scrub. As a reminder, for the 4.5 release, trac bug scrubs will be held weekly each Friday at 17:00 UTC. Bug scrubs are held in the #core channel of WordPress Slack.

The Slack archive for last week’s meeting begins here: https://wordpress.slack.com/archives/core/p1454691785001716

During the bug scrub, the following tickets were covered:

#25247, #34722, #27272, #22198, #14393, #19627, #34521, #35630, #35692, #20419, #35737, #34887, #34996, #33045, #30352, #35624, #15448, #35736

Today, on Friday, February 12 2016 at 17:00 UTC the bug scrub will run approximately 1 hour. Participants need not be present for the full duration, and everyone is welcome to attend.

We’ll start with a list of pre-submitted tickets, before going to an open floor.

If you would like to submit a ticket for consideration for the bug scrub, please comment below with the ticket number. If you have extensive knowledge of the ticket, attending or adding accompanying text which provides a brief description of each ticket, its current status, and what needs to happen for the ticket would be appreciated. Bug scrubs are a great way to get extra eyes on tickets, feedback on patches, or suggestions on future routes.

Note: this will be the last pre-submitted tickets/open-floor style bug scrub for this release. All bug scrubs after this will focus exclusively on tickets currently milestoned for this major release in order to help expedite the betas and release candidates of the 4.5 release. Normal open-floor/pre-submitted ticket bug scrubs will resume after the stable release of 4.5.

#bug-scrub, #trac-cleanup

Call for Trac Tickets and Recap of 1/29/2016 Bug Scrub

On Friday, January 29 at 17:00 UTC, we had our regularly scheduled bug scrub. As a reminder, for the 4.5 release, trac bug scrubs will be held weekly each Friday at 17:00 UTC. Bug scrubs are held in the #core channel of WordPress Slack.

The Slack archive for last week’s meeting begins here: https://wordpress.slack.com/archives/core/p1454086872000605

During the bug scrub, the following tickets were covered:

#35216, #27048, #35010, #34887, #35243, #32602, #26571, #33717, #14853, #34996, and #14134

Tomorrow, on Friday, February 4 2016 at 17:00 UTC the bug scrub will run approximately 1 hour. Participants need not be present for the full duration, and everyone is welcome to attend.

We’ll start with a list of pre-submitted tickets, before going to an open floor.

If you would like to submit a ticket for consideration for the bug scrub, please comment below with the ticket number. If you have extensive knowledge of the ticket, attending or adding accompanying text which provides a brief description of each ticket, its current status, and what needs to happen for the ticket would be appreciated. Bug scrubs are a great way to get extra eyes on tickets, feedback on patches, or suggestions on future routes.

#bug-scrub, #trac-cleanup

Call for Trac Tickets and Recap of 1/15/2016 Bug Scrub

On Friday January 15 at 17:00 UTC  we held the second regularly scheduled bug scrub of the WordPress 4.5 release cycle. As a reminder, for the 4.5 release, trac bug scrubs will be held weekly each Friday at 17:00 UTC. Bug scrubs are held in the #core channel of WordPress Slack.

Unfortunately, as I am unable to make today’s meeting, and was unable over the last few days to find a replacement, today’s meeting is cancelled. I hope to see you all at the next meeting, which will be next Friday at 17:00 UTC. Regardless, please feel free to use the time to triage tickets!

The Slack archive for last week’s meeting begins here: https://wordpress.slack.com/archives/core/p1452877403010570
During the bug scrub, the following tickets were covered:

#32318 , #32920 , #12955 , #25669 , #27056 , #28441 , #29660 , #34839 , #35100 , #13910 , #30352 , #2702 , #33045 , #33283 , #13459 , and #18877

Next week, the bug scrub will run approximately 1 hour. Participants need not be present for the full duration, and everyone is welcome to attend.

We’ll start with a list of pre-submitted tickets, before going to an open floor. As time permits, the remainder will be filled with a mix of tickets in the 4.5 milestone, and abandoned tickets, taken from report 43 (Ancient Tickets) on Trac.

If you would like to submit a ticket for consideration for the bug scrub, please comment below with the ticket number. If you have extensive knowledge of the ticket, accompanying text which provides  a brief description of each ticket, its current status, and what needs to happen for the ticket would be appreciated. Bug scrubs are a great way to get extra eyes on tickets, feedback on patches, or suggestions on future routes.

During the WordPress 4.4 cycle, Trac experienced a net loss of approximately 600 tickets. The goal for the 4.5 release is to get to 2,500 tickets open on Trac. The current count is 3,347, which is 847 tickets from this goal.

#bug-scrub, #trac-cleanup

Call for Trac Tickets and Recap of 1/8/2016 Bug Scrub

Today we held the first regularly scheduled bug scrub of the WordPress 4.5 release cycle. As a reminder, for the 4.5 release, trac bug scrubs will be held weekly each Friday at 17:00 UTC. The next meeting will be Friday at 17:00 UTC. Bug scrubs are held in the #core channel of WordPress Slack.

This week, we covered 4 trac tickets.

The Slack archive for this chat begins here: https://wordpress.slack.com/archives/core/p1452272470009065

Here is a list of the tickets covered:

  • #25650: When switching between blogs, wp_upload_dir ‘baseurl’ and ‘url’ may be pointing to the current blog not the switched one
  • #34406: wp_kses_hair is too stringent redux
  • #35160: Reorganize Feeds Unit Tests & Add Test Coverage for Atom
  • #15058: Validate option and transient name lengths

Next week, the bug scrub will run approximately 3 hours. Participants need not be present for the full duration, and everyone is welcome to attend.

We’ll start with a list of pre-submitted tickets, before going to an open floor. As time permits, the remainder will be filled with a mix of tickets in the 4.5 milestone, and abandoned tickets, taken from report 43 (Ancient Tickets) on Trac.

If you would like to submit a ticket for consideration for the bug scrub, please comment below with the ticket number. If you have extensive knowledge of the ticket, accompanying text which provides  a brief description of each ticket, its current status, and what needs to happen for the ticket would be appreciated. Bug scrubs are a great way to get extra eyes on tickets, feedback on patches, or suggestions on future routes.

During the WordPress 4.4 cycle, Trac experienced a net loss of approximately 600 tickets. The goal for the 4.5 release is to get to 2,500 tickets open on Trac. The current count is 3,347, which is 847 tickets from this goal.

#bug-scrub, #trac-cleanup