summaryrefslogtreecommitdiff
path: root/docs/internals/contributing/writing-code/submitting-patches.txt
diff options
context:
space:
mode:
authorTim Graham <timograham@gmail.com>2018-04-06 13:04:11 -0400
committerTim Graham <timograham@gmail.com>2018-04-06 20:46:06 -0400
commit3428be3cf95260e8e11b8ca2efb5f4e12da9ee8c (patch)
treed4b5926b8db03ed39395192b507053edd158bdc7 /docs/internals/contributing/writing-code/submitting-patches.txt
parent85d853b2d3a77e58a5d28fcdd4594b2766e6c202 (diff)
Updated contributing docs for some latest practices.
Diffstat (limited to 'docs/internals/contributing/writing-code/submitting-patches.txt')
-rw-r--r--docs/internals/contributing/writing-code/submitting-patches.txt4
1 files changed, 4 insertions, 0 deletions
diff --git a/docs/internals/contributing/writing-code/submitting-patches.txt b/docs/internals/contributing/writing-code/submitting-patches.txt
index 15dd431229..5bfff59b52 100644
--- a/docs/internals/contributing/writing-code/submitting-patches.txt
+++ b/docs/internals/contributing/writing-code/submitting-patches.txt
@@ -273,6 +273,10 @@ Bugs
* Is there a proper regression test (the test should fail before the fix
is applied)?
+* If it's a bug that :ref:`qualifies for a backport <supported-versions-policy>`
+ to the stable version of Django, is there a release note in
+ ``docs/releases/A.B.C.txt``? Bug fixes that will be applied only to the
+ master branch don't need a release note.
New Features
------------