innov
/
django1
1
0
Fork 0
Code Issues Pull Requests 1 Projects Releases Wiki Activity

Fixed #21108 -- Updated how to release docs: prereleases now go to PyPI.

This commit is contained in:
Tim Graham 2015-01-16 18:24:10 -05:00
parent 996292d649
commit d9edd2f68f
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -34,7 +34,7 @@ The short version of the steps involved is:
#. Upload the package(s) to the ``djangoproject.com`` server. #. Upload the package(s) to the ``djangoproject.com`` server.
#. Unless this is a pre-release, add the new version(s) to PyPI. #. Upload the new version(s) to PyPI.
#. Declare the new version in the admin on ``djangoproject.com``. #. Declare the new version in the admin on ``djangoproject.com``.
@ -315,7 +315,7 @@ Now you're ready to actually put the release out there. To do this:
#. Go to the `Add release page in the admin`__, enter the new release number #. Go to the `Add release page in the admin`__, enter the new release number
exactly as it appears in the name of the tarball (Django-<version>.tar.gz). exactly as it appears in the name of the tarball (Django-<version>.tar.gz).
So for example enter "1.5.1" or "1.4-rc-2", etc. If the release is part of So for example enter "1.5.1" or "1.4c2", etc. If the release is part of
an LTS branch, mark it so. an LTS branch, mark it so.
__ https://www.djangoproject.com/admin/releases/release/add/ __ https://www.djangoproject.com/admin/releases/release/add/