Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse code

Fixed #3658 -- Included description of ticket resolution states in the

contributors' documentation. Thanks, Simon Greenhill.


git-svn-id: http://code.djangoproject.com/svn/django/trunk@4682 bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
commit cdc79b71cb9d8ccd49542a728d8d4fc609f6f41c 1 parent 449ea76
Malcolm Tredinnick authored

Showing 1 changed file with 30 additions and 1 deletion. Show diff stats Hide diff stats

  1. 31  docs/contributing.txt
31  docs/contributing.txt
@@ -195,7 +195,7 @@ The second part of this workflow involves a set of flags the describe what the
195 195
 ticket has or needs in order to be "ready for checkin":
196 196
 
197 197
     "Has patch"
198  
-        The means the ticket has an associated patch_. These will be
  198
+        This means the ticket has an associated patch_. These will be
199 199
         reviewed to see if the patch is "good".
200 200
 
201 201
     "Needs documentation"
@@ -212,6 +212,35 @@ ticket has or needs in order to be "ready for checkin":
212 212
         ready for checkin. This could mean the patch no longer applies
213 213
         cleanly, or that the code doesn't live up to our standards.
214 214
 
  215
+A ticket can be resolved in a number of ways:
  216
+
  217
+    "fixed"
  218
+        This state is used by one of the core developers once a patch has been
  219
+        rolled into Django, and the issue is fixed.
  220
+
  221
+    "invalid"
  222
+        This state is used if the ticket is found to be incorrect, or a user
  223
+        error.
  224
+
  225
+    "wontfix"
  226
+        Used when a core developer decides that this request is not
  227
+        appropriate for consideration in Django. This is usually chosen after
  228
+        discussion in the ``django-developers`` mailing list, and you should
  229
+        feel free to join in when it's something you care about.
  230
+
  231
+    "duplicate"
  232
+        This is used when, rather obviously, there's a duplicate ticket about
  233
+        the same issue. By closing the extra tickets, we can keep all the
  234
+        discussion in one place which helps everyone.
  235
+
  236
+    "worksforme"
  237
+        This state is similar to "invalid", but is generally used to show
  238
+        that the triage team was unable to replicate the original bug.
  239
+
  240
+If you believe that the ticket was closed in error, either because you're still having the 
  241
+issue, or it's popped up somewhere else, or the triagers have made a mistake, please reopen
  242
+the ticket and tell us why.
  243
+
215 244
 .. _required details: `Reporting bugs`_
216 245
 .. _good patch: `Patch style`_
217 246
 .. _patch: `Submitting patches`_

0 notes on commit cdc79b7

Please sign in to comment.
Something went wrong with that request. Please try again.