diff options
| author | Sarah Boyce <42296566+sarahboyce@users.noreply.github.com> | 2025-02-05 13:11:35 +0100 |
|---|---|---|
| committer | Sarah Boyce <42296566+sarahboyce@users.noreply.github.com> | 2025-02-19 12:16:20 +0100 |
| commit | 463e87e249693d1fd810b925c2da2c71426929cf (patch) | |
| tree | 72134c322df404460c191c441f89d4d7ca2e7c26 /docs/internals/contributing/committing-code.txt | |
| parent | 9b7944896d9e96c60fe609308d152c358effdd39 (diff) | |
[5.2.x] Fixed #35908 -- Retired the django-developers and django-users mailing lists.
Co-authored-by: Chaitanya Rahalkar <chaitanyarahalkar@squareup.com>
Backport of 86493307f97b9795a74227b6af2d59a267160847 from main.
Diffstat (limited to 'docs/internals/contributing/committing-code.txt')
| -rw-r--r-- | docs/internals/contributing/committing-code.txt | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/docs/internals/contributing/committing-code.txt b/docs/internals/contributing/committing-code.txt index 91c6d21beb..2dc42d8853 100644 --- a/docs/internals/contributing/committing-code.txt +++ b/docs/internals/contributing/committing-code.txt @@ -109,14 +109,14 @@ Django's Git repository: discuss the situation with the team. * For any medium-to-big changes, where "medium-to-big" is according to - your judgment, please bring things up on the `Django Forum`_ or - |django-developers| mailing list before making the change. + your judgment, please bring things up on the `Django Forum`_ before making + the change. If you bring something up and nobody responds, please don't take that to mean your idea is great and should be implemented immediately because nobody contested it. Everyone doesn't always have a lot of time to read - mailing list discussions immediately, so you may have to wait a couple of - days before getting a response. + discussions immediately, so you may have to wait a couple of days before + getting a response. * Write detailed commit messages in the past tense, not present tense. @@ -228,14 +228,14 @@ 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 Forum`_ - or |django-developers| mailing list then revert if there are none. + 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 merger and the reverter-to-be then try - to work it out on the `Django Forum`_ or |django-developers| mailing list. If - an agreement can't be reached then it should be put to a vote. + to work it out on the `Django Forum`_ . If an agreement can't be reached then + it should be put to a vote. * If the commit introduced a confirmed, disclosed security vulnerability then the commit may be reverted immediately without |
