[wp-hackers] Unanswered tickets

[spencerp]

You know what would be nicer, is this:

a) Make a Ticket / with Patch storage bin. Have the storage bin separate 
from each branch/trunk versions. But have all the Tickets/ with Patches 
assigned to a specific version in the Trac Ticket Storage Bin. So, it 
would be like this:

Ticket Bin:
branch X.X.X/ - (XXX amount of tickets)
branch X.X.XX/ - (XXX amount of tickets)
Trunk X.X/ - (XXX amount of tickets)

Roadmap:
Milestone X.X.X - (X amount of tickets added from this branch/milestone 
ticket bin that the devs are sure to commit at a specific time frame)
Milestone X.X.XX - (X amount of tickets added from this branch/milestone 
ticket bin that the devs are sure to commit at a specific time frame)
Milestone X.X (Trunk) - (X amount of tickets added from this 
trunk/milestone ticket bin that the devs are sure to commit at a 
specific time frame)

I know it seems pointless, but it could help clean up things and keep 
things organized better. Rather than packing tickets under a milestone 
or trunk right away (resulting in ticket bumps from version to version) 
they could be stored in the "bin" and assigned to a specific version. 
Then chosen by the devs which ones to actually MOVE under the Milestones 
specifically that the devs are for sure going to commit at a given deadline.

THEN, the remaining "uncommitted" tickets/fixes for each specific 
Milestone will remain in the "bin" for later deciding of where it should 
go. There would really be much "bumping" of tickets at all then. Because 
the "uncertain ones" will remain in the "bin" until later or after 
finding the best place(s) for "it". So again, it would basically be like...

a) User submits new ticket, it ends up in the "bin" under that specific 
branch/trunk version. It sits in there until noticed, and then decided 
what to do with it. (This is how it is now of course, while sitting 
under each Milestone it's assigned. But I'm thinking of keeping things 
from being bumped constantly and or organized better, for when actually 
getting around to the tickets submitted there.)

b) Devs see a ticket/a handful of tickets that they really want to 
commit, they can just MOVE those tickets from the "bin", to under the 
specific milestone being worked on at the specific time. So "they" know 
this ticket, that ticket, and this ticket is going to be committed by X 
Date / Time Frame. And to help from weeding through TONS of tickets that 
probably won't ever make it in to begin with...

c) Tickets left in the "bin", can sit there and wait until a decision is 
made on what to do with them. Rather than constantly bumping from 
version to version Milestones.