diff options
| author | Unai Zalakain <unai@gisa-elkartea.org> | 2013-10-04 00:51:22 +0200 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2013-10-04 10:00:36 -0400 |
| commit | 3895d8899d7a01f2bdb1c206e45d8578a9739c91 (patch) | |
| tree | 6ab6dfa79cabbd968b846dde80d7d778b50dfb56 /docs/internals/contributing/committing-code.txt | |
| parent | 8b0014869f666b44cd20692e38073ec0a0a8cb08 (diff) | |
Fixed #21213 -- Added docs for Django's mailing lists.
Added docs/internals/mailing-lists.txt documenting the use of django's
mailing lists. All references across docs changed to point to this page.
The referencing makes use of substitution because there's no way to make
a :ref: link in a non-inline fashion in Sphinx. It also makes use of
rst_epilog Sphinx conf for making this substitutions across all the
docs.
Diffstat (limited to 'docs/internals/contributing/committing-code.txt')
| -rw-r--r-- | docs/internals/contributing/committing-code.txt | 9 |
1 files changed, 4 insertions, 5 deletions
diff --git a/docs/internals/contributing/committing-code.txt b/docs/internals/contributing/committing-code.txt index b81bdd2e04..72d0187cea 100644 --- a/docs/internals/contributing/committing-code.txt +++ b/docs/internals/contributing/committing-code.txt @@ -131,10 +131,10 @@ Django's Git repository: reasons for example) first discuss the situation with the core team. * For any medium-to-big changes, where "medium-to-big" is according to - your judgment, please bring things up on the `django-developers`_ + your judgment, please bring things up on the |django-developers| mailing list before making the change. - If you bring something up on `django-developers`_ and nobody responds, + If you bring something up on |django-developers| and nobody responds, please don't take that to mean your idea is great and should be implemented immediately because nobody contested it. Django's lead developers don't have a lot of time to read mailing-list discussions @@ -239,13 +239,13 @@ When a mistaken commit is discovered, please follow these guidelines: * If the original author can't be reached (within a reasonable amount of time -- a day or so) and the problem is severe -- crashing bug, major test failures, etc -- then ask for objections on the - `django-developers`_ mailing list then revert if there are none. + |django-developers| mailing list then revert if there are none. * If the problem is small (a feature commit after feature freeze, say), wait it out. * If there's a disagreement between the committer and the - reverter-to-be then try to work it out on the `django-developers`_ + reverter-to-be then try to work it out on the |django-developers| mailing list. If an agreement can't be reached then it should be put to a vote. @@ -260,5 +260,4 @@ When a mistaken commit is discovered, please follow these guidelines: For instance, if you did: ``git push upstream feature_antigravity``, just do a reverse push: ``git push upstream :feature_antigravity``. -.. _django-developers: http://groups.google.com/group/django-developers .. _ticket tracker: https://code.djangoproject.com/newticket |