summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorCarlton Gibson <carlton.gibson@noumenal.es>2021-04-10 17:29:32 +0200
committerCarlton Gibson <carlton.gibson@noumenal.es>2021-04-22 09:02:59 +0200
commit4c6345969215e6ed401e981383bdaad4e42623e3 (patch)
treee13327a0a3b5ceea7225352b3cca1f54b48c2764 /docs
parent7d7c6d9a3a75f7e0dfe1e7fb992e3c3a6068a87e (diff)
[3.2.x] Added note to update docs config when creating new stable branch.
django_next_version in docs/conf.py should be bumped when creating a new stable branch. Backport of 6a7af38b072f97d15e06aba87c673c16ecafe5a8 from main
Diffstat (limited to 'docs')
-rw-r--r--docs/internals/howto-release-django.txt5
1 files changed, 5 insertions, 0 deletions
diff --git a/docs/internals/howto-release-django.txt b/docs/internals/howto-release-django.txt
index ecd9a752f5..f889026bf9 100644
--- a/docs/internals/howto-release-django.txt
+++ b/docs/internals/howto-release-django.txt
@@ -140,6 +140,11 @@ any time leading up to the actual release:
$ git checkout -b stable/3.1.x origin/main
$ git push origin -u stable/3.1.x:stable/3.1.x
+ At the same time, update the ``django_next_version`` variable in
+ ``docs/conf.py`` on the stable release branch to point to the new
+ development version. For example, when creating ``stable/4.2.x``, set
+ ``django_next_version`` to ``'5.0'`` on the new branch.
+
#. If this is the "dot zero" release of a new series, create a new branch from
the current stable branch in the `django-docs-translations
<https://github.com/django/django-docs-translations>`_ repository. For