Let’s Garden Trac!

TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. has an overwhelming number of tickets in it. A lot of us gravitate towards specific components, or have our own way of slicing the master list into a customized view.

For those of us who have created an issue on Trac, we have the ability to view all of those tickets in one place, go here once logged in:
https://core.trac.wordpress.org/query

Tickets that we own:
https://core.trac.wordpress.org/my-tickets

Tickets we have patched:
https://core.trac.wordpress.org/my-patches

One of my favorite things to do is to scan the list of tickets that other users have created and look for inspiration for things to work on. Just change the “Reporter is” value to someone else’s username.

I want to encourage everyone to do the following

Look at the tickets you have created in the past and ask yourself:

• is this still relevant?
• has this been fixed already? if so, when?
• is the suggestion/premise obsolete?

Look at the tickets that you have created patches for in the past and find out:

• Does the 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. still apply?
• Can the solution be improved?
• Do I need to add unit tests?

For the tickets that you own:

• is the ticketticket Created for both bug reports and feature development on the bug tracker. a candidate for 4.4?
• is the ticket a candidate for commit?

I’ve been doing a TON of digging through Trac over the past 2 weeks. My hunch is that there are a lot of tickets that can retired. The BEST person to decide that for your old tickets is YOU!

#4-4