| | 1 | = Help on Ticket Changes = |
| | 2 | |
| | 3 | Inspired from a [http://groups.google.co.nz/group/django-developers/browse_thread/thread/a60a582d1e0a562b/ddf9676055b769bd?hl=en&#ddf9676055b769bd process discussion on django-developers], we're going to extend Trac to be a little more friendly when tickets are changed - a friendly summary of what it means and what to do next. |
| | 4 | |
| | 5 | This wiki page is a holding page for the text, please expand on it! |
| | 6 | |
| | 7 | * See also: [http://docs.djangoproject.com/en/dev/internals/contributing/ Contributing to Django] |
| | 8 | |
| | 9 | Goals: |
| | 10 | * Upbeat, friendly, clear language |
| | 11 | * Constructive suggestions |
| | 12 | * Try and explain the ''reason'' for the change, as well as ''what to do next''. |
| | 13 | * They'll have the comment from the person who changed the ticket just above any text thats here. |
| | 14 | |
| | 15 | == Ticket Resolutions == |
| | 16 | |
| | 17 | === duplicate === |
| | 18 | |
| | 19 | By closing duplicate tickets, we keep all the discussion about a topic in one place, which helps everyone. |
| | 20 | |
| | 21 | What do do next? |
| | 22 | 1. Check out the linked ticket that is referred to above. |
| | 23 | 2. Add any relevant notes/patches/discussion from here to the other ticket. |
| | 24 | 3. If you don't agree that it's a duplicate, please reopen the ticket and explain why (mistakes do happen!). |
| | 25 | |
| | 26 | === fixed === |
| | 27 | |
| | 28 | Awesome! Congratulations, it's done & made it to trunk! Please find another ticket (link to Accepted: tickets on trac?) and lets go! |
| | 29 | |
| | 30 | === invalid === |
| | 31 | |
| | 32 | It seems the ticket is actually the result of a user error, describes a problem with something other than the core Django framework itself, or is really a support query. |
| | 33 | |
| | 34 | What to do next? |
| | 35 | 1. If it's been suggested that it's a user error or support query, please ask on (django-users) or in IRC at #django |
| | 36 | 2. If your ticket refers to a 3rd party Django or Python application, please file the issue with them. Google will help you track down their home. |
| | 37 | 3. If you don't agree, please reopen the ticket and explain why (mistakes do happen!). |
| | 38 | |
| | 39 | === wontfix === |
| | 40 | |
| | 41 | Used when a core developer decides that this request is not appropriate for consideration in Django. This is usually chosen after discussion in the django-developers mailing list, and you should feel free to join in when it’s something you care about. |
| | 42 | |
| | 43 | What to do next? |
| | 44 | 1. ... something ... |
| | 45 | |
| | 46 | === worksforme === |
| | 47 | |
| | 48 | Used when the ticket doesn’t contain enough detail to replicate the original bug. |
| | 49 | |
| | 50 | What to do next? |
| | 51 | 1. ... something ... |
| | 52 | |
| | 53 | == Ticket Flags == |
| | 54 | |
| | 55 | === Has Patch === |
| | 56 | |
| | 57 | ''I don't think we need one for this, actual next-steps will be covered by one of the other flags anyway?'' |
| | 58 | |
| | 59 | === Needs documentation === |
| | 60 | |
| | 61 | This flag is used for tickets with patches that need associated documentation. Complete documentation of features is a prerequisite before we can check a fix into the codebase. |
| | 62 | |
| | 63 | What to do next? |
| | 64 | 1. ... something ... |
| | 65 | |
| | 66 | === Needs tests === |
| | 67 | |
| | 68 | This flags the patch as needing associated unit tests. Again, this is a required part of a valid patch. |
| | 69 | |
| | 70 | What to do next? |
| | 71 | 1. ... something ... |
| | 72 | |
| | 73 | === Patch needs improvement === |
| | 74 | |
| | 75 | This flag means that although the ticket has a patch, it’s not quite ready for checkin. This could mean the patch no longer applies cleanly, or that the code doesn’t live up to our standards. |
| | 76 | |
| | 77 | What to do next? |
| | 78 | 1. ... something ... |
| | 79 | |