I’ve been reviewing how we manage trac tickets to try to improve how we manage and prioritise feature requests and suggestions. We have many great ideas in our Future Release milestone, but all too-often that’s become the place where great ideas go to die. At time of writing, the milestone contains nearly 700 tickets, and not even I know what’s good in there, or even what was once good but now redundant.
Our current workflow is: new ticket -> [Awaiting Review] -> [Under Consideration] -> [Future Release] or [Release Milestone] or closed ticket.
“Under Consideration” is where new suggestions live while we evaluate them and gather further feedback and comment. This is a relatively recent addition in the last couple of years, and it’s helped seperate tickets we haven’t looked at yet (“Awaiting Review”) to those we are looking at.
I propose we should try tweaking how we approach the “Future Release” milestone so we gain better understanding and awareness of vetted suggestions and bug reports, which in turn will help existing and new contributors find exciting tasks to work on. Et voilà!
- At the top of the pyramid, we have the two next release milestones (major and minor releases) which will work the same as they do today.
- “Up Next” is a new milestone containing important or strategic tickets that our regular contributors have expressed in working on within the next two releases.
- “Maybe Later” is a new milestone containing tickets that our regular contributors have decided that we have significant interest in working on, or are of a strategic importance, but less so than those in “Up Next”.
- “Awaiting Contributions” is a new milestone. It contains tickets that our regular contributors have decided would be valuable enhancements for BuddyPress, but which are unlikely to be worked on by those regular contributors for the forseeable future — because they are less important than those in the other milestones.
- This is pyramid-shaped on purpose. The milestones at the bottom should always contain more tickets than those at the top.
If this idea has support, we’ll have to spend alot of time reviewing the entire Future Release milestone, which is a great opportunity to close any tickets that are now irrelevant for some reason. The “Future Release” name itself would no longer be used to avoid confusion.
I would be very happy to hear your feedback on the proposed milestone changes (would they work? are they solving the right problem?).