Tag Archives: trac cleanup

Jb Audras 5:18 pm on January 24, 2023
Tags: , trac cleanup, , WP20   

Proposal: Old Tickets Trac Triage Sessions

In a few months, we will celebrate the 20th anniversary of WordPress!

To mark the milestone, what could be better than taking a look at all of our old TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets?

This post aims to put together several 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 sessions dedicated to old tickets that haunt the depths of Trac, the ticketticket Created for both bug reports and feature development on the bug tracker. tool used for the development of WordPress.

To date, on Trac, we have for example:

Goal of the “Old Tickets Trac Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. Sessions” initiative

The purpose of these sessions would be to take the oldest tickets, qualify them and move them forward according to their content or status.

  • Some tickets are probably no longer relevant today with the recent evolution of WordPress, in this case they must be closed as outdated (though this resolution status doesn’t exist in Trac for the moment)
  • Some tickets may require new discussions, this will be an opportunity to discuss them by adding new comments
  • Some tickets may be ready, but don’t have a patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. yet, we may be able to find people to take care of it and milestone them accordingly
  • Some tickets also probably have a patch (check for the has-patch workflow keyword), but this one needs to be refreshed (check for the needs-refresh  workflow keyword). In that case we could find someone to take care of it and milestone them accordingly
  • Other tickets may have a patch ready to go (must be quite rare), in this case the idea would be to move them directly to the next milestones (WP 6.2 or 6.3)

How to participate?

Everyone is invited to contribute to this initiative. There could be several types of sessions:

  • “Classic” triage sessions on the 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/. Make, coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. channel, where we would review tickets (read the dedicated post on the Core handbook: Leading a bug scrub)
  • Local triage sessions: local communities, or even companies, are welcome to organize an event to help move forward old tickets

During the meeting, the idea is to take one of the Trac reports listed at the beginning of this post and to go through each ticket.

What can I do to help move a ticket forward?

Depending on its status and progress, several types of contributions can help move a ticket forward:

  • Mark as close tickets that are no longer relevant. A Bug Gardener or a Component Maintainer will close it later
  • Extend the discussion to try to find how to move towards a resolution
  • Try to reproduce a bug that has not been reproduced yet, then share the steps of the reproduction procedure as well as screenshots or screencasts (when applicable)
  • Propose a patch, for tickets that do not yet have one, if the ticket is relevant and the existing discussion has resulted in a conclusion
  • Test existing patches and share screenshots or screencast (when applicable), using the test report template
  • Refresh an existing patch, if the ticket contains a patch that no longer applies to the current state of the WordPress source code

Some of these actions require a developer profile, others are accessible to anyone who knows enough WordPress and is able to run a test site.

Planned meetings

Let’s start with a first session on the Make Slack #core channel on Thursday, January 26, 2023 at 15:00 UTC. This session will last about 1 hour, and everyone is welcome!

If you are interested in hosting an “Old Tickets Trac Triage Session”, feel free to comment on this post!

For more info, read the dedicated post on the Core handbook: Leading a bug scrub.

Planned meetings, as confirmed,will be added to the list below:

DateLocationOrganizer
January 26, 2023 at 15:00 UTC“Classic” triage session on Slack (core channel)@audrasjb
February 9, 2023 at 15:00 UTC“Classic” triage session on Slack (core channel)@audrasjb
March 2, 2023 at 15:00 UTC“Classic” triage session on Slack (core channel)@audrasjb
March 23, 2023 at 15:00 UTC“Classic” triage session on Slack (core channel)@audrasjb
Another dateA locationYour name here!

This proposal is a follow-up to a discussion on Twitter with @defries and other WordPress contributors.

Props to @defries, @webcommsat and @costdev for proofreading.

#trac-cleanup, #triage, #wp20

chriscct7 4:46 pm on February 16, 2016
Tags: , trac cleanup   

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

As announced previously, for the next two weeks only, 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 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 enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. 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, 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 normally weekly each 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/..

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

chriscct7 5:49 am on February 12, 2016
Tags: , 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 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. 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. 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/..

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 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, 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 releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope. 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

chriscct7 11:04 pm on February 4, 2016
Tags: , 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 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. 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. 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/..

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 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, 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

chriscct7 8:36 am on January 22, 2016
Tags: , 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 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 release 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. 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/..

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 triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. 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 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

chriscct7 10:58 pm on January 8, 2016
Tags: , trac cleanup   

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 release 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