mirrors/django
mirrors/django
0
0
Fork 0
mirror of https://github.com/django/django.git synced 2024-12-01 15:42:04 +01:00
Code Issues Releases Wiki Activity

Updated release process in the "How is Django Formed?" documentation.

Browse Source 
* Fixed Trac's post release step.
* Doc'd the use of robots_txt for updating robots.docs.txt.
This commit is contained in:
Mariusz Felisiak 2019-05-24 11:05:52 +02:00 committed by Carlton Gibson
parent 85195dd237
commit 1d25354fb5
1 changed files with 13 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
docs/internals/howto-release-django.txt
View File

@ -345,7 +345,13 @@ Now you're ready to actually put the release out there. To do this:
Create new ``DocumentRelease`` objects for each language that has an entry
for the previous release. Update djangoproject.com's `robots.docs.txt`__
file by copying entries from the previous release.
file by copying entries from ``manage_translations.py robots_txt`` from the
current stable branch in the ``django-docs-translations`` repository. For
example, when releasing Django 2.2::
$ git checkout stable/2.2.x
$ git pull
$ python manage_translations.py robots_txt
__ https://github.com/django/djangoproject.com/blob/master/djangoproject/static/robots.docs.txt
@ -368,8 +374,12 @@ You're almost done! All that's left to do now is:
``VERSION = (1, 5, 2, 'alpha', 0)``.
#. 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.
default by changing the ``default_version`` setting in the
code.djangoproject.com's `trac.ini`__, if it's a final release). The new X.Y
version should be added after the alpha release and the default version
should be updated after "dot zero" release.
__ https://github.com/django/code.djangoproject.com/blob/master/trac-env/conf/trac.ini
#. If this was a security release, update :doc:`/releases/security` with
details of the issues addressed.