summaryrefslogtreecommitdiff
path: root/docs/internals/howto-release-django.txt
diff options
context:
space:
mode:
Diffstat (limited to 'docs/internals/howto-release-django.txt')
-rw-r--r--docs/internals/howto-release-django.txt13
1 files changed, 8 insertions, 5 deletions
diff --git a/docs/internals/howto-release-django.txt b/docs/internals/howto-release-django.txt
index a49251da76..fd985ddafc 100644
--- a/docs/internals/howto-release-django.txt
+++ b/docs/internals/howto-release-django.txt
@@ -175,13 +175,13 @@ OK, this is the fun part, where we actually push out a release!
#. Make sure you have an absolutely clean tree by running ``git clean -dfx``.
-#. Run ``python setup.py sdist`` to generate the release package. This will
- create the release package in a ``dist/`` directory.
+#. Run ``make -f extras/Makefile`` to generate the release packages. This will
+ create the release packages in a ``dist/`` directory.
-#. Generate the hashes of the release package::
+#. Generate the hashes of the release packages::
- $ md5sum dist/Django-<version>.tar.gz
- $ sha1sum dist/Django-<version>.tar.gz
+ $ md5sum dist/Django-*
+ $ sha1sum dist/Django-*
*FIXME: perhaps we should switch to sha256?*
@@ -221,6 +221,9 @@ Now you're ready to actually put the release out there. To do this:
$ mktmpenv
$ pip install https://www.djangoproject.com/m/releases/1.5/Django-1.5.1.tar.gz
$ deactivate
+ $ mktmpenv
+ $ pip install https://www.djangoproject.com/m/releases/1.5/Django-1.5.1-py2.py3-none-any.whl
+ $ deactivate
This just tests that the tarballs are available (i.e. redirects are up) and
that they install correctly, but it'll catch silly mistakes.