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

Today we held the first regularly scheduled 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 of the WordPress 4.5 releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software. cycle. As a reminder, for the 4.5 release, tracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. 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 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/..

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 blogblog (versus network, site) 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 ticketticket Created for both bug reports and feature development on the bug tracker. 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