From d9edd2f68f6edaa5e634a7d93b29fe97cb7312fe Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Fri, 16 Jan 2015 18:24:10 -0500 Subject: [PATCH] Fixed #21108 -- Updated how to release docs: prereleases now go to PyPI. --- docs/internals/howto-release-django.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/internals/howto-release-django.txt b/docs/internals/howto-release-django.txt index 0f293d575b..56a9de9d40 100644 --- a/docs/internals/howto-release-django.txt +++ b/docs/internals/howto-release-django.txt @@ -34,7 +34,7 @@ The short version of the steps involved is: #. 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``. @@ -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 exactly as it appears in the name of the tarball (Django-.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. __ https://www.djangoproject.com/admin/releases/release/add/