p15693087
/
django
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Added a note about creating new doc versions; update stable doc version before announcement.

This commit is contained in:
Carl Meyer 2013-02-26 14:46:46 -07:00
parent 58a2fc820e
commit bd669e47d7
1 changed files with 11 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -255,11 +255,6 @@ Now you're ready to actually put the release out there. To do this:
#. Make the blog post announcing the release live. #. Make the blog post announcing the release live.
#. Post the release announcement to the django-announce,
django-developers and django-users mailing lists. This should
include links to both the announcement blog post and the release
notes. *FIXME: make some templates with example text*.
#. For a new version release (e.g. 1.5, 1.6), update the default stable version #. For a new version release (e.g. 1.5, 1.6), update the default stable version
of the docs by flipping the ``is_default`` flag to ``True`` on the of the docs by flipping the ``is_default`` flag to ``True`` on the
appropriate ``DocumentRelease`` object in the ``docs.djangoproject.com`` appropriate ``DocumentRelease`` object in the ``docs.djangoproject.com``
@ -267,6 +262,11 @@ Now you're ready to actually put the release out there. To do this:
others). *FIXME: I had to do this via fab managepy:shell,docs but we should others). *FIXME: I had to do this via fab managepy:shell,docs but we should
probably make it possible to do via the admin.* probably make it possible to do via the admin.*
#. Post the release announcement to the django-announce,
django-developers and django-users mailing lists. This should
include links to both the announcement blog post and the release
notes. *FIXME: make some templates with example text*.
Post-release Post-release
============ ============
@ -277,6 +277,12 @@ You're almost done! All that's left to do now is:
example, after releasing 1.2.1, update ``VERSION`` to report "1.2.2 example, after releasing 1.2.1, update ``VERSION`` to report "1.2.2
pre-alpha". *FIXME: Is this correct? Do we still do this?* pre-alpha". *FIXME: Is this correct? Do we still do this?*
#. For the first alpha release of a new version (when we create the
``stable/1.?.x`` git branch), you'll want to create a new
``DocumentRelease`` object in the ``docs.djangoproject.com`` database for
the new version's docs, and update the ``docs/fixtures/doc_releases.json``
JSON fixture. *FIXME: what is the purpose of maintaining this fixture?*
Notes on setting the VERSION tuple Notes on setting the VERSION tuple
================================== ==================================