summaryrefslogtreecommitdiff
path: root/docs/internals
diff options
context:
space:
mode:
authorClaude Paroz <claude@2xlibre.net>2017-04-15 09:19:06 -0400
committerTim Graham <timograham@gmail.com>2017-04-15 09:19:16 -0400
commit89a080fc0541b3f918abd392982263d5e00d403f (patch)
treeffd5fd0db3f5adc47322f34f008867fced916e86 /docs/internals
parent941b8691351d4739cd9391b0a1326abd0b1c29c0 (diff)
Doc'd a release task for translated docs.
Diffstat (limited to 'docs/internals')
-rw-r--r--docs/internals/howto-release-django.txt6
1 files changed, 6 insertions, 0 deletions
diff --git a/docs/internals/howto-release-django.txt b/docs/internals/howto-release-django.txt
index 8316beea75..bfa42614ef 100644
--- a/docs/internals/howto-release-django.txt
+++ b/docs/internals/howto-release-django.txt
@@ -338,6 +338,12 @@ Now you're ready to actually put the release out there. To do this:
database (this will automatically flip it to ``False`` for all
others); you can do this using the site's admin.
+ 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.
+
+ __ https://github.com/django/djangoproject.com/blob/master/djangoproject/static/robots.docs.txt
+
#. Post the release announcement to the |django-announce|, |django-developers|,
and |django-users| mailing lists. This should include a link to the
announcement blog post. If this is a security release, also include