From 4b8563e9f6faf8b237ec6d7d62c9f4d3b6d5aaa6 Mon Sep 17 00:00:00 2001 From: Natalia <124304+nessita@users.noreply.github.com> Date: Wed, 26 Nov 2025 13:23:42 -0300 Subject: [6.0.x] Included usage of new scripts in docs/internals/howto-release-django.txt. Backport of 60b08ad5e1701b1a9b2a03e5897670d5af32d379 from main. --- docs/internals/howto-release-django.txt | 32 +++++++++++++++++++++++++++----- 1 file changed, 27 insertions(+), 5 deletions(-) (limited to 'docs') diff --git a/docs/internals/howto-release-django.txt b/docs/internals/howto-release-django.txt index 4a8dd6483c..5425f5f43c 100644 --- a/docs/internals/howto-release-django.txt +++ b/docs/internals/howto-release-django.txt @@ -471,12 +471,25 @@ Building the artifacts .. admonition:: Optionally use helper scripts You can streamline some of the steps below using helper scripts from the - Wiki: + ``scripts`` folder: - * `Release script - `_ - * `Test new version script - `_ + * Release script example run: + + .. code-block:: shell + + $ PGP_KEY_ID= PGP_KEY_URL= DEST_FOLDER=~/releases scripts/do_django_release.py + + * Test new version script: + + .. code-block:: shell + + $ VERSION=5.2.1 scripts/test_new_version.sh + + * Confirm release signature script: + + .. code-block:: shell + + $ VERSION=5.2.1 scripts/confirm_release.sh #. Tag the release using ``git tag``. For example: @@ -693,6 +706,15 @@ You're almost done! All that's left to do now is: #. Update djangoproject.com's download page (`example PR `__). + #. Process the older versions that will reach End-Of-Mainstream and/or + End-Of-Life support when this final release is published: + + #. Ensure that the EOL versions are mentioned in the blog post. `Example + `_. + + #. Create a tag for the EOL stable branch and delete the stable branch. + Inspect and use the ``scripts/archive_eol_stable_branches.py`` helper. + #. If this was a security release, update :doc:`/releases/security` with details of the issues addressed. -- cgit v1.3