#15516: Update the ticket life cycle diagram
-------------------------------------+-------------------------------------
Reporter: ramiro | Owner: tswicegood
Type: | Status: new
Cleanup/optimization | Component: Documentation
Milestone: | Severity: Normal
Version: SVN | Keywords:
Resolution: | Has patch: 0
Triage Stage: Accepted | Needs tests: 0
Needs documentation: 0 | Easy pickings: 0
Patch needs improvement: 0 |
UI/UX: 0 |
-------------------------------------+-------------------------------------
Comment (by julien):
Looks pretty awesome! I just had a few remarks:
* "Needs Info" is a resolution, which means that the ticket will get
closed. The ticket may then be reopened if more information can be
provided.
* In principle, no ticket in the "Accepted" stage would directly be
checked in. In general someone first needs to review the patch and then
move it to "Ready for checkin" before a committer checks it in. A rare
exception to this principle is a committer jumps this step if he/she
approves the patch and is ready to commit it right away.
* An free and open format would be preferable for the source file to make
sure anyone can update it. Maybe SVG?
Thanks for the great work!
--
Ticket URL: <https://code.djangoproject.com/ticket/15516#comment:6>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
