From f16abe44a1ec1dda46a962af4d32405b20c78c1c Mon Sep 17 00:00:00 2001 From: Baptiste Mispelon Date: Wed, 6 Nov 2013 18:05:16 +0100 Subject: [PATCH] Added missing info to the release checklist. --- docs/internals/howto-release-django.txt | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/docs/internals/howto-release-django.txt b/docs/internals/howto-release-django.txt index 3cbc124b64..ac89f7db20 100644 --- a/docs/internals/howto-release-django.txt +++ b/docs/internals/howto-release-django.txt @@ -299,7 +299,8 @@ Now you're ready to actually put the release out there. To do this: #. Go to the `Add release page in the admin`__, enter the new release number exactly as it appears in the name of the tarball (Django-.tar.gz). - So for example enter "1.5.1" or "1.4-rc-2", etc. + So for example enter "1.5.1" or "1.4-rc-2", etc. If the release is part of + an LTS branch, mark it so. __ https://www.djangoproject.com/admin/releases/release/add/ @@ -332,8 +333,9 @@ You're almost done! All that's left to do now is: JSON fixture, so people without access to the production DB can still run an up-to-date copy of the docs site. -#. Add the release in `Trac's versions list`_ if necessary. Not all versions - are declared; take example on previous releases. +#. Add the release in `Trac's versions list`_ if necessary (and make it the + default if it's a final release). Not all versions are declared; + take example on previous releases. .. _Trac's versions list: https://code.djangoproject.com/admin/ticket/versions