Changes between Version 73 and Version 74 of TracTicketTriage

Timestamp:

Jan 12, 2015, 9:42:14 PM (9 years ago)

Author:

figaro

Comment:

Cosmetic changes

TracTicketTriage

@@ -3 +3 @@
 This page lists guidelines and conventions used within the Trac project for [http://en.wikipedia.org/wiki/Triage triage] of tickets.
 
-As a matter of fact, we happen to mainly focus on the Milestone information to decide whether a ticket has been triaged or not. Therefore, still to be triaged tickets can be found in queries specifying an unset milestone, like query:status!=closed&milestone= or report:20.
+We focus on the Milestone information to decide whether a ticket has been triaged or not. Therefore, still to be triaged tickets can be found in queries specifying an unset milestone, such as query:status!=closed&milestone= or report:20.
 
 There are currently:
  - [[TicketQuery(status!=closed,milestone=,keywords!~=needinfo,format=count)]] untriaged tickets
- - [[TicketQuery(status!=closed,keywords~=needinfo,format=count)]] tickets for which we're waiting for feedback
- - [[TicketQuery(status!=closed,milestone!=,format=count)]] valid tickets to work on...
+ - [[TicketQuery(status!=closed,keywords~=needinfo,format=count)]] tickets for which more feedback is required
+ - [[TicketQuery(status!=closed,milestone!=,format=count)]] valid tickets to work on
 
 == How to help? ==
 
-First, there is a good deal of tickets which are not yet triaged. Anyone with some knowledge about the Trac project can help us to apply the triaging rules, in order to detect duplicate requests, eliminate invalid tickets and identify the real issues by assigning them a milestone.
- - tickets which are targeting a software which has nothing to do with Trac should be closed as //invalid// with the **WrongTrac** mention in the comment
- - tickets which are targeting a Trac plugin should be closed as //cantfix// with the **PluginIssue** mention in the comment. If the identity of the plugin is easily determined, add the `TH:<Plugin>` mention.
+Anyone with some knowledge about the Trac project can help us to apply the triaging rules, to detect duplicate requests, eliminate invalid tickets and identify the real issues by assigning them a milestone.
+ - tickets which have nothing to do with Trac should be closed as //invalid// with the **WrongTrac** mention in the comment
+ - tickets regarding a Trac plugin should be closed as //cantfix// with the **PluginIssue** mention in the comment. If the identity of the plugin is easily determined, add the `TH:<Plugin>` mention.
    - if the plugin is "agilo", then mention **AgiloForScrum** and add support@agile42.com to the CC: 
  - tickets which are clearly about installation issues or support requests should be invalidated as well, qualifying it as an **InstallationIssue** and directing the reporter to the MailingList.
  - for complaints about the long inactivity on opened tickets, refer to **ThisTicketWasOpenedTenYearsAgo** 
 
-For the tickets that are waiting for user feedback, anyone can help as well: close tickets which haven't received the requested feedback since a few months or further process them if they received some feedback.
+For the tickets that are waiting for user feedback, anyone can help as well: close tickets which haven't received the requested feedback since a few months or further process them if they received feedback.
 
 Finally, among the valid tickets, [query:status!=closed&milestone!=&keywords!~=needinfo&type=defect&group=milestone many are categorized as defects]. Those should probably get the most attention or be recategorized as enhancements if they are not real defects.
 
 == Milestone ==
+=== Dos ===
+
  * If resolution is `fixed`, the Milestone should be set accordingly to the RoadMap. See report:36 for tickets that should be corrected one day.
  * If resolution is `duplicate`, `cantfix`, `wontfix`, `invalid` or `worksforme` the Milestone should be blank. See report:35 for tickets that should be corrected.
+ * If the ticket is valid and related to Trac, but no developer is planning to work on it for a next release, use [milestone:unscheduled].
+ * If the ticket is valid and related to Trac, but not directly related to a release, use [milestone:"not applicable"].
+
+=== Don'ts ===
 
  * Don't assign a milestone without a reason or patch.
  * Don't modify a milestone as ''anonymous'' and without a reason.
  * Don't assign a milestone of a bugfix only release (e.g. 0.10.5) to enhancement request tickets.
-
- * If the ticket is valid and related to Trac, but no developer is planning to work on it for a next release, use [milestone:unscheduled].
- * If the ticket is valid and related to Trac, but not directly related to a release, use [milestone:"not applicable"].
 
 == Status and Resolution ==
@@ -47 +50 @@
      - In original request: ''#2345 has been marked as duplicate of this ticket''
    * We usually let open the ticket which contains the most up-to-the-point discussion about the issue, the one which contains an appropriate patch, or other than that, the oldest ticket.
-   * Finally, if it's the n^th^ time such a duplicate has been created, it's about time to list it in the ticket duplicates hall of fame, i.e. the MostFrequentDuplicates page.
+   * Finally, if it's the n^th^ time such a duplicate has been created, list it in the ticket duplicates hall of fame, i.e. the MostFrequentDuplicates page.
 
 And also, don't close or reopen a ticket without a reason.
@@ -60 +63 @@
 == Ticket Description ==
 
-Only administrators can edit ticket descriptions.  They are only edited to fix formatting errors, not the actual content. Occasionally, we may also add editorial notes, in order to not spread misleading information, e.g. #4297 or to summarize the current status of a long running issue, e.g. #4132 or #2611. In all cases, it should be quite clear from the formatting what's coming from the original author and what has been annotated afterwards.
+Only administrators can edit ticket descriptions. They are only edited to fix formatting errors, not the actual content. Occasionally, we may also add editorial notes, in order to not spread misleading information, e.g. #4297 or to summarize the current status of a long running issue, e.g. #4132 or #2611. In all cases, it should be quite clear from the formatting what's coming from the original author and what has been annotated afterwards.
 
 == Keywords ==
@@ -139 +142 @@
    [kwquery:solaris],
    [kwquery:macosx]
- - Presentation issues
+ - Presentation issues:
    * [kwquery:layout], issues with the organization of the pages
    * [kwquery:navigation], main and meta navigation issues
@@ -155 +158 @@
      [kwquery:safari],
      [kwquery:chrome]
- - Other kinds of grouping
+ - Other kinds of grouping:
    * [kwquery:crash] -- There's a segmentation fault or other serious OS level error implied.
    * [kwquery:memory] -- Out of memory condition, most probably involving memory leaks.
@@ -172 +175 @@
  * ''eblot'': Following the update Matt did on #4222, I think we also need to document what is / would be the policy for outdated Trac releases (criteria to declare as wontfix, etc.)
 
-
 '''Policy for closing tickets'''
 
@@ -180 +182 @@
  * Avoid closing tickets without a comment of the reporter
    * This is especially true if the reporter is an active contributor
- * be open minded, and accept that the existent processes have some deficits (for sure there are documentation deficits, that's why this document was initiated) [comment:ticket:4174:15 see #4174]
+ * be open minded, and accept that the existing processes have some deficiencies [comment:ticket:4174:15 see #4174]
  * core developers have final authority to close tickets