#26359: explain dual ticket tracking system
-------------------------------+------------------------------------
Reporter: beckastar | Owner: nobody
Type: Uncategorized | Status: new
Component: Documentation | Version: 1.9
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------+------------------------------------
Changes (by freakboy3742):
* needs_better_patch: => 0
* needs_docs: => 0
* component: Uncategorized => Documentation
* needs_tests: => 0
* stage: Unreviewed => Accepted
Comment:
There aren't any *tickets* on GitHub - we've disabled the Issues feature
on our Github account. However, we do accept Pull Requests on GitHub,
which have a number that is very similar to a ticket.
So, if you're reporting a problem, you need to use Trac; when you submit a
pull request, that PR will be given a number, and that number should
reference the Trac issue number.
I know this is a bit confusing, so improved documentation is definitely a
good idea. The source of the problem is that GitHub's ticket system isn't
practical for a large project like Django, and we had a legacy of 20000
tickets in Trac (many of which had a significant history) that couldn't be
imported into GitHub when we moved our repository there.
--
Ticket URL: <https://code.djangoproject.com/ticket/26359#comment:1>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.725823f55dea235c913ebb1d4555dce4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
