Changes between Version 43 and Version 44 of TracTicketTriage

Timestamp:

Apr 7, 2007, 4:36:37 PM (17 years ago)

Author:

Christian Boos

Comment:

Rename the none milestone to not applicable. none was quite too similar to None, as shown in custom queries grouped by milestones.

TracTicketTriage

@@ -1 +1 @@
 = Trac Project Ticket Triage =
-
-(document status: under development - please provide feedback to increase clarity and completeness)
 
 This page lists guidelines and conventions used within the Trac project for [http://en.wikipedia.org/wiki/Triage triage] of tickets.
@@ -11 +9 @@
  * Don't assign a milestone without a reason or patch.
  * Don't modify a milestone as ''anonymous'' and without a reason.
- * If adding an enhancement request ticket, don't set the milestone to a bugfix only release (e.g. 0.10.2).
+ * If adding an enhancement request ticket, don't set the milestone to a bugfix only release (e.g. 0.10.5).
  * If the feature is more or less a blue sky idea, then use [milestone:2.0]
  * If the bug or feature seems doable in a reasonable time frame, but doesn't seem to fit in the current schedule, use [milestone:1.0]
- * If there's no milestone corresponding to a past or future Trac release which seems to be adequate, but the ticket is nevertheless valid and has to be processed further, then the milestone can be set to [milestone:none].
+ * If there's no milestone corresponding to a past or future Trac release which seems to be adequate, but the ticket is nevertheless valid and has to be processed further, then the milestone can be set to [milestone:"not applicable"]. This rule is needed as long as we don't have a better way to distinguish among triaged and non-triaged tickets.
 
 == Status and Resolution ==