| Version 1 (modified by , 15 years ago) ( diff ) |
|---|
Help on Ticket Changes
Inspired from a 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.
This wiki page is a holding page for the text, please expand on it!
- See also: Contributing to Django
Goals:
- Upbeat, friendly, clear language
- Constructive suggestions
- Try and explain the reason for the change, as well as what to do next.
- They'll have the comment from the person who changed the ticket just above any text thats here.
Ticket Resolutions
duplicate
By closing duplicate tickets, we keep all the discussion about a topic in one place, which helps everyone.
What do do next?
- Check out the linked ticket that is referred to above.
- Add any relevant notes/patches/discussion from here to the other ticket.
- If you don't agree that it's a duplicate, please reopen the ticket and explain why (mistakes do happen!).
fixed
Awesome! Congratulations, it's done & made it to trunk! Please find another ticket (link to Accepted: tickets on trac?) and lets go!
invalid
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.
What to do next?
- If it's been suggested that it's a user error or support query, please ask on (django-users) or in IRC at #django
- 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.
- If you don't agree, please reopen the ticket and explain why (mistakes do happen!).
wontfix
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.
What to do next?
- ... something ...
worksforme
Used when the ticket doesn’t contain enough detail to replicate the original bug.
What to do next?
- ... something ...
Ticket Flags
Has Patch
I don't think we need one for this, actual next-steps will be covered by one of the other flags anyway?
Needs documentation
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.
What to do next?
- ... something ...
Needs tests
This flags the patch as needing associated unit tests. Again, this is a required part of a valid patch.
What to do next?
- ... something ...
Patch needs improvement
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.
What to do next?
- ... something ...