Remy Blank wrote:
> Christian Boos wrote:
>
>> Not to mention that {20} has grown to 211 tickets ... Hm.
>>
>
> I volunteer to make a first filtering pass through these. Quite often,
> it's a "will do" / "won't do" decision, which might be quite subjective.
>
I'd suggest the following triage workflow:
- The ticket is likely bogus (WrongTrac, installation issue, invalid,
etc.) => close as wontfix
I suggest making an InstallationIssue page for quick closing, as I did
with the WrongTrac one, which serves its purpose most of the time.
- The ticket is an interesting enhancement idea: you like it and think
you can do it, then choose the milestone that seems fit, otherwise make
that 2.0 (and no owner).
- The ticket seems to be a valid bug report:
- for 0.10.x => unless it comes with a patch, close as wontfix,
0.10.x being de facto unsupported (except maybe for security issues
which anyway are not to be discussed in tickets, TracTenSupport page?)
- for 0.11.x => schedule that for 0.11.3 if it seems important,
0.11.x for later (*)
- for 0.12.x => obviously for the 0.12 milestone
If the issue seems to be related to a deeper problem in Trac, for 0.13
if you fell optimistic, 1.0 otherwise.
Add the 'needinfo', 'patch', and 'verify' keywords as needed for further
processing. Exhaustive list of semi-standardized keywords can be found
in TracTicketTriage.
(*) I just had the idea of creating a "0.11.x" milestone which would
serve as a placeholder for tickets affecting 0.11-stable, instead of
having constantly to move tickets around.
Current 0.11.3 will be renamed 0.11-retriage, as it currently contains a
mix of stuff that should be dispatched to other milestones according to
the guidelines above.
> So I suggest that I try to reduce this list by closing or assigning
> tickets to a milestone, and others keep an eye on me and correct the bad
> decisions by re-opening or re-assigning as they see fit.
>
> Opinions?
Sure, please go ahead. I'll create 0.11.x and 0.11-retriage shortly.
-- Christian
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac
Development" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/trac-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
