Changes between Version 2 and Version 3 of NewTicketGuidelines

Timestamp:

Apr 8, 2010, 10:07:19 AM (14 years ago)

Author:

Christian Boos

Comment:

emphasize a few points, in particular the need to keep the milestone empty when creating new tickets so that they can be triaged

NewTicketGuidelines

@@ -45 +45 @@
    To that end, it's usually necessary to give the following information:
    - ''How To Reproduce'': describe what you were doing when the problem happened. 
-     Someone following those instructions should be able to reproduce the problem.
+     //**Someone following those instructions should be able to reproduce the problem.**//
    - ''System Information'': list the software components involved with their version 
      - the Operating System
@@ -57 +57 @@
    - ''Python backtrace'': if you have one, append it at the end of the description, 
      enclosed in a `{{{` ... `}}}` block.
- - The following ticket fields should be correctly set:
+ - The following ticket fields //**should be correctly set by you**//:
    - The '''Version''' of the Trac software you were using. This can usually be seen in the ''About'' page.
    - The '''Component''' specifies the subsystem of Trac in which the error happened or where the enhancement should be made
    - The '''Severity''' is a rough estimation of the impact of the problem or the importance of the enhancement
    - The '''Keywords''' can contain a few important words about the issue (though we tend to use some conventions about the keywords themselves, see TracTicketTriage#Keywords for more details).
- - The following ticket fields can be left as they are:
-   - The '''Assign to''' person will be deduced from the choice of the ''component''
+ - The following ticket fields //**should be left empty**//:
+   - The '''Assign to''' person will be the developer taking responsibility for the ticket, or the patch contributor if the patch is good enough to be mostly applied as is
    - The '''Priority''' will be arbitrarily set by a Trac developer ;)
-   - The '''Milestone''' will be set after the [TracTicketTriage ticket triage]. 
-     An empty milestone means the ticket has not yet been triaged.
+   - The '''Milestone''' will also be set by us **after** the [TracTicketTriage ticket triage]. 
+     So it's important to leave the  milestone field ''empty'', which is used by us as an indicator that the ticket has not yet been triaged.
 
 Please take all these guidelines with a grain of salt, those are not strict rules, only hints for improving the ongoing development process of Trac itself!