diff options
| author | Mariusz Felisiak <felisiak.mariusz@gmail.com> | 2023-09-19 08:22:31 +0200 |
|---|---|---|
| committer | Natalia <124304+nessita@users.noreply.github.com> | 2023-09-19 09:29:25 -0300 |
| commit | c70f08c4aa55b097fceb53f68392887d9ac2fd16 (patch) | |
| tree | a5490ea324fc409cf1ab58b28d40777f633c6c98 | |
| parent | d485aa2732e4219756c99120a8326cc33b291e34 (diff) | |
[4.2.x] Added updating the Django release process on Trac to release steps.
Backport of 7c1cf585e80114b6e531b40bd2954406d033afe3 from main
| -rw-r--r-- | docs/internals/howto-release-django.txt | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/docs/internals/howto-release-django.txt b/docs/internals/howto-release-django.txt index 4b63f6ec82..5c2d0b7451 100644 --- a/docs/internals/howto-release-django.txt +++ b/docs/internals/howto-release-django.txt @@ -432,6 +432,10 @@ You're almost done! All that's left to do now is: __ https://github.com/django/code.djangoproject.com/blob/main/trac-env/conf/trac.ini +#. If it's a final release, update the current stable branch and remove the + pre-release branch in the `Django release process + <https://code.djangoproject.com/#Djangoreleaseprocess>`_ on Trac. + #. If this was a security release, update :doc:`/releases/security` with details of the issues addressed. @@ -479,6 +483,10 @@ need to be done by the releaser. <https://github.com/pypa/trove-classifiers/issues/29>`_. For example ``Framework :: Django :: 3.1``. +#. Update the current branch under active development and add pre-release + branch in the `Django release process + <https://code.djangoproject.com/#Djangoreleaseprocess>`_ on Trac. + Notes on setting the VERSION tuple ================================== |