diff options
| author | Gabriel Hurley <gabehr@gmail.com> | 2011-02-27 22:13:07 +0000 |
|---|---|---|
| committer | Gabriel Hurley <gabehr@gmail.com> | 2011-02-27 22:13:07 +0000 |
| commit | 2b7b4683257c072f74b03358ccc368831b872671 (patch) | |
| tree | 10ac0136d18b102f535e43fb15b9130834254828 /docs/howto | |
| parent | 28123d715389d85e78b757287baedf577d71c4a9 (diff) | |
Fixed #14702 -- Added a "needsinfo" resolution to Trac, and added supporting documentation on the new resolution and closing tickets in general.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@15665 bcc190cf-cafb-0310-a4f2-bffc1f526a37
Diffstat (limited to 'docs/howto')
| -rw-r--r-- | docs/howto/contribute.txt | 35 |
1 files changed, 35 insertions, 0 deletions
diff --git a/docs/howto/contribute.txt b/docs/howto/contribute.txt index eb1dd105cc..286c9282c7 100644 --- a/docs/howto/contribute.txt +++ b/docs/howto/contribute.txt @@ -64,6 +64,8 @@ However, Trac can be quite confusing even to veteran contributors. Having to look at both flags and triage stages isn't immediately obvious, and the stages
themselves can be misinterpreted.
+.. _triage-stages-explained:
+
What Django's triage stages "really mean"
-----------------------------------------
@@ -135,6 +137,39 @@ will eventually be merged to trunk. Tickets in this stage generally don't need further work. This may happen in the case of major features/refactors in each
release cycle, or as part of the annual Google Summer of Code efforts.
+.. _closing-tickets:
+
+Closing Tickets
+---------------
+
+When a ticket has completed its useful lifecycle, it's time for it to be closed.
+Closing a ticket is a big responsibility, though. You have to be sure that
+the issue is really resolved, and you need to keep in mind that the reporter
+of the ticket may not be happy to have their ticket closed (unless it's fixed,
+of course). If you're not certain about closing a ticket, just leave a comment
+with your thoughts instead.
+
+If you do close a ticket, you should always make sure of the following:
+
+ * Be certain that the issue is resolved.
+
+ * Leave a comment explaining the decision to close the ticket.
+
+ * If there is a way they can improve the ticket to reopen it, let them know.
+
+ * If the ticket is a duplicate, reference the original ticket.
+
+ * **Be polite.** No one likes having their ticket closed. It can be
+ frustrating or even discouraging. The best way to avoid turning people
+ off from contributing to Django is to be polite and friendly and to offer
+ suggestions for how they could improve this ticket and other tickets in the
+ future.
+
+.. seealso::
+
+ The :ref:`contributing reference <ticket-resolutions>` contains a
+ description of each of the available resolutions in Trac.
+
Example Trac workflow
---------------------
|