From 541aa2434d5c8f40e991aafb24fde4084b5ab048 Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Mon, 19 Oct 2015 21:01:28 -0400 Subject: [PATCH] Removed "how to release Django" steps for 1.4 (no longer supported). --- docs/internals/howto-release-django.txt | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-) diff --git a/docs/internals/howto-release-django.txt b/docs/internals/howto-release-django.txt index 0da90ae374..12a06d31ef 100644 --- a/docs/internals/howto-release-django.txt +++ b/docs/internals/howto-release-django.txt @@ -191,11 +191,6 @@ OK, this is the fun part, where we actually push out a release! Please see `notes on setting the VERSION tuple`_ below for details on ``VERSION``. - In 1.4, the version number in ``docs/conf.py`` and ``setup.py`` should also - be updated. Here's `an example commit updating version numbers`__ for that. - - __ https://github.com/django/django/commit/592187e11b934f83153133cd5b3a246a881359e7 - #. If this is a pre-release package, update the "Development Status" trove classifier in ``setup.py`` to reflect this. Otherwise, make sure the classifier is set to ``Development Status :: 5 - Production/Stable``. @@ -211,8 +206,7 @@ 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 ``make -f extras/Makefile`` to generate the release packages. This will - create the release packages in a ``dist/`` directory. Note that we don't - publish wheel files for 1.4. + create the release packages in a ``dist/`` directory. #. Generate the hashes of the release packages::