<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>How is Django Formed? — Django 1.6.8 documentation</title>
<link rel="stylesheet" href="../_static/default.css" type="text/css" />
<link rel="stylesheet" href="../_static/pygments.css" type="text/css" />
<script type="text/javascript">
var DOCUMENTATION_OPTIONS = {
URL_ROOT: '../',
VERSION: '1.6.8',
COLLAPSE_INDEX: false,
FILE_SUFFIX: '.html',
HAS_SOURCE: true
};
</script>
<script type="text/javascript" src="../_static/jquery.js"></script>
<script type="text/javascript" src="../_static/underscore.js"></script>
<script type="text/javascript" src="../_static/doctools.js"></script>
<link rel="top" title="Django 1.6.8 documentation" href="../index.html" />
<link rel="up" title="Django internals" href="index.html" />
<link rel="prev" title="The Django source code repository" href="git.html" />
<script type="text/javascript" src="../templatebuiltins.js"></script>
<script type="text/javascript">
(function($) {
if (!django_template_builtins) {
// templatebuiltins.js missing, do nothing.
return;
}
$(document).ready(function() {
// Hyperlink Django template tags and filters
var base = "../ref/templates/builtins.html";
if (base == "#") {
// Special case for builtins.html itself
base = "";
}
// Tags are keywords, class '.k'
$("div.highlight\\-html\\+django span.k").each(function(i, elem) {
var tagname = $(elem).text();
if ($.inArray(tagname, django_template_builtins.ttags) != -1) {
var fragment = tagname.replace(/_/, '-');
$(elem).html("<a href='" + base + "#" + fragment + "'>" + tagname + "</a>");
}
});
// Filters are functions, class '.nf'
$("div.highlight\\-html\\+django span.nf").each(function(i, elem) {
var filtername = $(elem).text();
if ($.inArray(filtername, django_template_builtins.tfilters) != -1) {
var fragment = filtername.replace(/_/, '-');
$(elem).html("<a href='" + base + "#" + fragment + "'>" + filtername + "</a>");
}
});
});
})(jQuery);
</script>
</head>
<body>
<div class="document">
<div id="custom-doc" class="yui-t6">
<div id="hd">
<h1><a href="../index.html">Django 1.6.8 documentation</a></h1>
<div id="global-nav">
<a title="Home page" href="../index.html">Home</a> |
<a title="Table of contents" href="../contents.html">Table of contents</a> |
<a title="Global index" href="../genindex.html">Index</a> |
<a title="Module index" href="../py-modindex.html">Modules</a>
</div>
<div class="nav">
« <a href="git.html" title="The Django source code repository">previous</a>
|
<a href="index.html" title="Django internals" accesskey="U">up</a></div>
</div>
<div id="bd">
<div id="yui-main">
<div class="yui-b">
<div class="yui-g" id="internals-howto-release-django">
<div class="section" id="s-how-is-django-formed">
<span id="how-is-django-formed"></span><h1>How is Django Formed?<a class="headerlink" href="#how-is-django-formed" title="Permalink to this headline">¶</a></h1>
<p>This document explains how to release Django. If you’re unlucky enough to
be driving a release, you should follow these instructions to get the
package out.</p>
<p><strong>Please, keep these instructions up-to-date if you make changes!</strong> The point
here is to be descriptive, not proscriptive, so feel free to streamline or
otherwise make changes, but <strong>update this document accordingly!</strong></p>
<div class="section" id="s-overview">
<span id="overview"></span><h2>Overview<a class="headerlink" href="#overview" title="Permalink to this headline">¶</a></h2>
<p>There are three types of releases that you might need to make</p>
<ul class="simple">
<li>Security releases, disclosing and fixing a vulnerability. This’ll
generally involve two or three simultaneous releases – e.g.
1.5.x, 1.6.x, and, depending on timing, perhaps a 1.7 alpha/beta/rc.</li>
<li>Regular version releases, either a final release (e.g. 1.5) or a
bugfix update (e.g. 1.5.1).</li>
<li>Pre-releases, e.g. 1.6 beta or something.</li>
</ul>
<p>In general the steps are about the same regardless, but there are a few
differences noted. The short version is:</p>
<ol class="arabic simple">
<li>If this is a security release, pre-notify the security distribution list
at least one week before the actual release.</li>
<li>Proofread (and create if needed) the release notes, looking for
organization, writing errors, deprecation timelines, etc. Draft a blog post
and email announcement.</li>
<li>Update version numbers and create the release package(s)!</li>
<li>Upload the package(s) to the <tt class="docutils literal"><span class="pre">djangoproject.com</span></tt> server.</li>
<li>Unless this is a pre-release, add the new version(s) to PyPI.</li>
<li>Declare the new version in the admin on <tt class="docutils literal"><span class="pre">djangoproject.com</span></tt>.</li>
<li>Post the blog entry and send out the email announcements.</li>
<li>Update version numbers post-release.</li>
</ol>
<p>There are a lot of details, so please read on.</p>
</div>
<div class="section" id="s-prerequisites">
<span id="prerequisites"></span><h2>Prerequisites<a class="headerlink" href="#prerequisites" title="Permalink to this headline">¶</a></h2>
<p>You’ll need a few things hooked up to make this work:</p>
<ul class="simple">
<li>A GPG key recorded as an acceptable releaser in the <a class="reference external" href="https://www.djangoproject.com/m/pgp/django-releasers.txt">Django releasers</a>
document. (If this key is not your default signing key, you’ll need to add
<tt class="docutils literal"><span class="pre">-u</span> <span class="pre">you@example.com</span></tt> to every GPG signing command below, where
<tt class="docutils literal"><span class="pre">you@example.com</span></tt> is the email address associated with the key you want to
use.)</li>
<li>Access to Django’s record on PyPI.</li>
<li>Access to the <tt class="docutils literal"><span class="pre">djangoproject.com</span></tt> server to upload files and trigger a
deploy.</li>
<li>Access to the admin on <tt class="docutils literal"><span class="pre">djangoproject.com</span></tt> as a “Site maintainer”.</li>
<li>Access to post to <tt class="docutils literal"><span class="pre">django-announce</span></tt>.</li>
<li>If this is a security release, access to the pre-notification distribution
list.</li>
</ul>
<p>If this is your first release, you’ll need to coordinate with James and/or
Jacob to get all these things lined up.</p>
</div>
<div class="section" id="s-pre-release-tasks">
<span id="pre-release-tasks"></span><h2>Pre-release tasks<a class="headerlink" href="#pre-release-tasks" title="Permalink to this headline">¶</a></h2>
<p>A few items need to be taken care of before even beginning the release process.
This stuff starts about a week before the release; most of it can be done
any time leading up to the actual release:</p>
<ol class="arabic simple">
<li>If this is a security release, send out pre-notification <strong>one week</strong>
before the release. We maintain a list of who gets these pre-notification
emails at <em>FIXME WHERE?</em>. This email should be signed by the key you’ll use
for the release, and should include patches for each issue being fixed.</li>
<li>If this is a major release, make sure the tests pass, then increase
the default PBKDF2 iterations in
<tt class="docutils literal"><span class="pre">django.contrib.auth.hashers.PBKDF2PasswordHasher</span></tt> by about 10%
(pick a round number). Run the tests, and update the 3 failing
hasher tests with the new values. Make sure this gets noted in the
release notes (see release notes on 1.6 for an example).</li>
<li>As the release approaches, watch Trac to make sure no release blockers
are left for the upcoming release.</li>
<li>Check with the other committers to make sure they don’t have any
un-committed changes for the release.</li>
<li>Proofread the release notes, including looking at the online
version to catch any broken links or reST errors, and make sure the
release notes contain the correct date.</li>
<li>Double-check that the release notes mention deprecation timelines
for any APIs noted as deprecated, and that they mention any changes
in Python version support.</li>
<li>Double-check that the release notes index has a link to the notes
for the new release; this will be in <tt class="docutils literal"><span class="pre">docs/releases/index.txt</span></tt>.</li>
</ol>
</div>
<div class="section" id="s-preparing-for-release">
<span id="preparing-for-release"></span><h2>Preparing for release<a class="headerlink" href="#preparing-for-release" title="Permalink to this headline">¶</a></h2>
<p>Write the announcement blog post for the release. You can enter it into the
admin at any time and mark it as inactive. Here are a few examples: <a class="reference external" href="https://www.djangoproject.com/weblog/2013/feb/19/security/">example
security release announcement</a>, <a class="reference external" href="https://www.djangoproject.com/weblog/2012/mar/23/14/">example regular release announcement</a>,
<a class="reference external" href="https://www.djangoproject.com/weblog/2012/nov/27/15-beta-1/">example pre-release announcement</a>.</p>
</div>
<div class="section" id="s-actually-rolling-the-release">
<span id="actually-rolling-the-release"></span><h2>Actually rolling the release<a class="headerlink" href="#actually-rolling-the-release" title="Permalink to this headline">¶</a></h2>
<p>OK, this is the fun part, where we actually push out a release!</p>
<ol class="arabic">
<li><p class="first">Check <a class="reference external" href="http://djangoci.com">Jenkins</a> is green for the version(s) you’re putting out. You
probably shouldn’t issue a release until it’s green.</p>
</li>
<li><p class="first">A release always begins from a release branch, so you should make sure
you’re on a stable branch and up-to-date. For example:</p>
<div class="highlight-python"><pre>git checkout stable/1.5.x
git pull</pre>
</div>
</li>
<li><p class="first">If this is a security release, merge the appropriate patches from
<tt class="docutils literal"><span class="pre">django-private</span></tt>. Rebase these patches as necessary to make each one a
simple commit on the release branch rather than a merge commit. To ensure
this, merge them with the <tt class="docutils literal"><span class="pre">--ff-only</span></tt> flag; for example:</p>
<div class="highlight-python"><pre>git checkout stable/1.5.x
git merge --ff-only security/1.5.x</pre>
</div>
<p>(This assumes <tt class="docutils literal"><span class="pre">security/1.5.x</span></tt> is a branch in the <tt class="docutils literal"><span class="pre">django-private</span></tt> repo
containing the necessary security patches for the next release in the 1.5
series.)</p>
<p>If git refuses to merge with <tt class="docutils literal"><span class="pre">--ff-only</span></tt>, switch to the security-patch
branch and rebase it on the branch you are about to merge it into (<tt class="docutils literal"><span class="pre">git</span>
<span class="pre">checkout</span> <span class="pre">security/1.5.x;</span> <span class="pre">git</span> <span class="pre">rebase</span> <span class="pre">stable/1.5.x</span></tt>) and then switch back and
do the merge. Make sure the commit message for each security fix explains
that the commit is a security fix and that an announcement will follow
(<a class="reference external" href="https://github.com/django/django/commit/3ef4bbf495cc6c061789132e3d50a8231a89406b">example security commit</a>)</p>
</li>
<li><p class="first">Update version numbers for the release. This has to happen in three
places: <tt class="docutils literal"><span class="pre">django/__init__.py</span></tt>, <tt class="docutils literal"><span class="pre">docs/conf.py</span></tt>, and <tt class="docutils literal"><span class="pre">setup.py</span></tt>.
Please see <a class="reference internal" href="#notes-on-setting-the-version-tuple">notes on setting the VERSION tuple</a> below for details
on <tt class="docutils literal"><span class="pre">VERSION</span></tt>. Here’s <a class="reference external" href="https://github.com/django/django/commit/18d920ea4839fb54f9d2a5dcb555b6a5666ee469">an example commit updating version numbers</a></p>
</li>
<li><p class="first">If this is a pre-release package, update the “Development Status” trove
classifier in <tt class="docutils literal"><span class="pre">setup.py</span></tt> to reflect this. Otherwise, make sure the
classifier is set to <tt class="docutils literal"><span class="pre">Development</span> <span class="pre">Status</span> <span class="pre">::</span> <span class="pre">5</span> <span class="pre">-</span> <span class="pre">Production/Stable</span></tt>.</p>
</li>
<li><p class="first">Tag the release using <tt class="docutils literal"><span class="pre">git</span> <span class="pre">tag</span></tt>. For example:</p>
<div class="highlight-python"><pre>git tag --sign --message="Django 1.5.1" 1.5.1</pre>
</div>
<p>You can check your work by running <tt class="docutils literal"><span class="pre">git</span> <span class="pre">tag</span> <span class="pre">--verify</span> <span class="pre"><tag></span></tt>.</p>
</li>
<li><p class="first">Push your work, including the tag: <tt class="docutils literal"><span class="pre">git</span> <span class="pre">push</span> <span class="pre">--tags</span></tt>.</p>
</li>
<li><p class="first">Make sure you have an absolutely clean tree by running <tt class="docutils literal"><span class="pre">git</span> <span class="pre">clean</span> <span class="pre">-dfx</span></tt>.</p>
</li>
<li><p class="first">Run <tt class="docutils literal"><span class="pre">make</span> <span class="pre">-f</span> <span class="pre">extras/Makefile</span></tt> to generate the release packages. This will
create the release packages in a <tt class="docutils literal"><span class="pre">dist/</span></tt> directory.</p>
</li>
<li><p class="first">Generate the hashes of the release packages:</p>
<div class="highlight-python"><pre>$ md5sum dist/Django-*
$ sha1sum dist/Django-*</pre>
</div>
</li>
<li><p class="first">Create a “checksums” file containing the hashes and release information.
Start with this template and insert the correct version, date, release URL
and checksums:</p>
<div class="highlight-python"><pre>This file contains MD5 and SHA1 checksums for the source-code tarball
of Django <<VERSION>>, released <<DATE>>.
To use this file, you will need a working install of PGP or other
compatible public-key encryption software. You will also need to have
the Django release manager's public key in your keyring; this key has
the ID ``0x3684C0C08C8B2AE1`` and can be imported from the MIT
keyserver. For example, if using the open-source GNU Privacy Guard
implementation of PGP::
gpg --keyserver pgp.mit.edu --recv-key 0x3684C0C08C8B2AE1
Once the key is imported, verify this file::
gpg --verify <<THIS FILENAME>>
Once you have verified this file, you can use normal MD5 and SHA1
checksumming applications to generate the checksums of the Django
package and compare them to the checksums listed below.
Release package:
================
Django <<VERSION>>: https://www.djangoproject.com/m/releases/<<URL>>
MD5 checksum:
=============
MD5(<<RELEASE TAR.GZ FILENAME>>)= <<MD5SUM>>
SHA1 checksum:
==============
SHA1(<<RELEASE TAR.GZ FILENAME>>)= <<SHA1SUM>></pre>
</div>
</li>
<li><p class="first">Sign the checksum file (<tt class="docutils literal"><span class="pre">gpg</span> <span class="pre">--clearsign</span>
<span class="pre">Django-<version>.checksum.txt</span></tt>). This generates a signed document,
<tt class="docutils literal"><span class="pre">Django-<version>.checksum.txt.asc</span></tt> which you can then verify using <tt class="docutils literal"><span class="pre">gpg</span>
<span class="pre">--verify</span> <span class="pre">Django-<version>.checksum.txt.asc</span></tt>.</p>
</li>
</ol>
<p>If you’re issuing multiple releases, repeat these steps for each release.</p>
</div>
<div class="section" id="s-making-the-release-s-available-to-the-public">
<span id="making-the-release-s-available-to-the-public"></span><h2>Making the release(s) available to the public<a class="headerlink" href="#making-the-release-s-available-to-the-public" title="Permalink to this headline">¶</a></h2>
<p>Now you’re ready to actually put the release out there. To do this:</p>
<ol class="arabic">
<li><p class="first">Upload the release package(s) to the djangoproject server; releases go
in <tt class="docutils literal"><span class="pre">/home/www/djangoproject.com/src/media/releases</span></tt>, under a
directory for the appropriate version number (e.g.
<tt class="docutils literal"><span class="pre">/home/www/djangoproject.com/src/media/releases/1.5</span></tt> for a <tt class="docutils literal"><span class="pre">1.5.x</span></tt>
release.).</p>
</li>
<li><p class="first">Upload the checksum file(s); these go in
<tt class="docutils literal"><span class="pre">/home/www/djangoproject.com/src/media/pgp</span></tt>.</p>
</li>
<li><p class="first">Test that the release packages install correctly using <tt class="docutils literal"><span class="pre">easy_install</span></tt>
and <tt class="docutils literal"><span class="pre">pip</span></tt>. Here’s one method (which requires <a class="reference external" href="https://pypi.python.org/pypi/virtualenvwrapper">virtualenvwrapper</a>):</p>
<div class="highlight-python"><pre>$ mktmpenv
$ easy_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.tar.gz
$ deactivate
$ mktmpenv
$ pip install https://www.djangoproject.com/m/releases/1.5/Django-1.5.1-py2.py3-none-any.whl
$ deactivate</pre>
</div>
<p>This just tests that the tarballs are available (i.e. redirects are up) and
that they install correctly, but it’ll catch silly mistakes.</p>
</li>
<li><p class="first">Ask a few people on IRC to verify the checksums by visiting the checksums
file (e.g. <a class="reference external" href="https://www.djangoproject.com/m/pgp/Django-1.5b1.checksum.txt">https://www.djangoproject.com/m/pgp/Django-1.5b1.checksum.txt</a>)
and following the instructions in it. For bonus points, they can also unpack
the downloaded release tarball and verify that its contents appear to be
correct (proper version numbers, no stray <tt class="docutils literal"><span class="pre">.pyc</span></tt> or other undesirable
files).</p>
</li>
<li><p class="first">If this is a release that should land on PyPI (i.e. anything except for
a pre-release), register the new package with PyPI by running
<tt class="docutils literal"><span class="pre">python</span> <span class="pre">setup.py</span> <span class="pre">register</span></tt>.</p>
</li>
<li><p class="first">Upload the sdist you generated a few steps back through the PyPI web
interface. You’ll log into PyPI, click “Django” in the right sidebar,
find the release you just registered, and click “files” to upload the
sdist.</p>
<div class="admonition note">
<p class="first admonition-title">Note</p>
<p class="last">Why can’t we just use <tt class="docutils literal"><span class="pre">setup.py</span> <span class="pre">sdist</span> <span class="pre">upload</span></tt>? Well, if we do it above
that pushes the sdist to PyPI before we’ve had a chance to sign, review
and test it. And we can’t just <tt class="docutils literal"><span class="pre">setup.py</span> <span class="pre">upload</span></tt> without <tt class="docutils literal"><span class="pre">sdist</span></tt>
because <tt class="docutils literal"><span class="pre">setup.py</span></tt> prevents that. Nor can we <tt class="docutils literal"><span class="pre">sdist</span> <span class="pre">upload</span></tt> because
that would generate a <em>new</em> sdist that might not match the file we just
signed. Finally, uploading through the web interface is somewhat more
secure: it sends the file over HTTPS.</p>
</div>
</li>
<li><p class="first">Go to the <a class="reference external" href="https://www.djangoproject.com/admin/releases/release/add/">Add release page in the admin</a>, enter the new release number
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.</p>
</li>
<li><p class="first">Make the blog post announcing the release live.</p>
</li>
<li><p class="first">For a new version release (e.g. 1.5, 1.6), update the default stable version
of the docs by flipping the <tt class="docutils literal"><span class="pre">is_default</span></tt> flag to <tt class="docutils literal"><span class="pre">True</span></tt> on the
appropriate <tt class="docutils literal"><span class="pre">DocumentRelease</span></tt> object in the <tt class="docutils literal"><span class="pre">docs.djangoproject.com</span></tt>
database (this will automatically flip it to <tt class="docutils literal"><span class="pre">False</span></tt> for all
others); you can do this using the site’s admin.</p>
</li>
<li><p class="first">Post the release announcement to the <a class="reference internal" href="mailing-lists.html#django-announce-mailing-list"><em>django-announce</em></a>,
<a class="reference internal" href="mailing-lists.html#django-developers-mailing-list"><em>django-developers</em></a> and <a class="reference internal" href="mailing-lists.html#django-users-mailing-list"><em>django-users</em></a> mailing lists. This should
include links to the announcement blog post and the release notes.</p>
</li>
</ol>
</div>
<div class="section" id="s-post-release">
<span id="post-release"></span><h2>Post-release<a class="headerlink" href="#post-release" title="Permalink to this headline">¶</a></h2>
<p>You’re almost done! All that’s left to do now is:</p>
<ol class="arabic simple">
<li>Update the <tt class="docutils literal"><span class="pre">VERSION</span></tt> tuple in <tt class="docutils literal"><span class="pre">django/__init__.py</span></tt> again,
incrementing to whatever the next expected release will be. For
example, after releasing 1.5.1, update <tt class="docutils literal"><span class="pre">VERSION</span></tt> to
<tt class="docutils literal"><span class="pre">VERSION</span> <span class="pre">=</span> <span class="pre">(1,</span> <span class="pre">5,</span> <span class="pre">2,</span> <span class="pre">'alpha',</span> <span class="pre">0)</span></tt>.</li>
<li>For the first alpha release of a new version (when we create the
<tt class="docutils literal"><span class="pre">stable/1.?.x</span></tt> git branch), you’ll want to create a new
<tt class="docutils literal"><span class="pre">DocumentRelease</span></tt> object in the <tt class="docutils literal"><span class="pre">docs.djangoproject.com</span></tt> database for
the new version’s docs, and update the <tt class="docutils literal"><span class="pre">docs/fixtures/doc_releases.json</span></tt>
JSON fixture, so people without access to the production DB can still
run an up-to-date copy of the docs site.</li>
<li>Add the release in <a class="reference external" href="https://code.djangoproject.com/admin/ticket/versions">Trac’s versions list</a> if necessary. Not all versions
are declared; take example on previous releases.</li>
</ol>
</div>
<div class="section" id="s-notes-on-setting-the-version-tuple">
<span id="notes-on-setting-the-version-tuple"></span><h2>Notes on setting the VERSION tuple<a class="headerlink" href="#notes-on-setting-the-version-tuple" title="Permalink to this headline">¶</a></h2>
<p>Django’s version reporting is controlled by the <tt class="docutils literal"><span class="pre">VERSION</span></tt> tuple in
<tt class="docutils literal"><span class="pre">django/__init__.py</span></tt>. This is a five-element tuple, whose elements
are:</p>
<ol class="arabic simple">
<li>Major version.</li>
<li>Minor version.</li>
<li>Micro version.</li>
<li>Status – can be one of “alpha”, “beta”, “rc” or “final”.</li>
<li>Series number, for alpha/beta/RC packages which run in sequence
(allowing, for example, “beta 1”, “beta 2”, etc.).</li>
</ol>
<p>For a final release, the status is always “final” and the series
number is always 0. A series number of 0 with an “alpha” status will
be reported as “pre-alpha”.</p>
<p>Some examples:</p>
<ul class="simple">
<li><tt class="docutils literal"><span class="pre">(1,</span> <span class="pre">2,</span> <span class="pre">1,</span> <span class="pre">'final',</span> <span class="pre">0)</span></tt> –> “1.2.1”</li>
<li><tt class="docutils literal"><span class="pre">(1,</span> <span class="pre">3,</span> <span class="pre">0,</span> <span class="pre">'alpha',</span> <span class="pre">0)</span></tt> –> “1.3 pre-alpha”</li>
<li><tt class="docutils literal"><span class="pre">(1,</span> <span class="pre">3,</span> <span class="pre">0,</span> <span class="pre">'beta',</span> <span class="pre">2)</span></tt> –> “1.3 beta 2”</li>
</ul>
</div>
</div>
</div>
</div>
</div>
<div class="yui-b" id="sidebar">
<div class="sphinxsidebar">
<div class="sphinxsidebarwrapper">
<h3><a href="../contents.html">Table Of Contents</a></h3>
<ul>
<li><a class="reference internal" href="#">How is Django Formed?</a><ul>
<li><a class="reference internal" href="#overview">Overview</a></li>
<li><a class="reference internal" href="#prerequisites">Prerequisites</a></li>
<li><a class="reference internal" href="#pre-release-tasks">Pre-release tasks</a></li>
<li><a class="reference internal" href="#preparing-for-release">Preparing for release</a></li>
<li><a class="reference internal" href="#actually-rolling-the-release">Actually rolling the release</a></li>
<li><a class="reference internal" href="#making-the-release-s-available-to-the-public">Making the release(s) available to the public</a></li>
<li><a class="reference internal" href="#post-release">Post-release</a></li>
<li><a class="reference internal" href="#notes-on-setting-the-version-tuple">Notes on setting the VERSION tuple</a></li>
</ul>
</li>
</ul>
<h3>Browse</h3>
<ul>
<li>Prev: <a href="git.html">The Django source code repository</a></li>
</ul>
<h3>You are here:</h3>
<ul>
<li>
<a href="../index.html">Django 1.6.8 documentation</a>
<ul><li><a href="index.html">Django internals</a>
<ul><li>How is Django Formed?</li></ul>
</li></ul>
</li>
</ul>
<h3>This Page</h3>
<ul class="this-page-menu">
<li><a href="../_sources/internals/howto-release-django.txt"
rel="nofollow">Show Source</a></li>
</ul>
<div id="searchbox" style="display: none">
<h3>Quick search</h3>
<form class="search" action="../search.html" method="get">
<input type="text" name="q" />
<input type="submit" value="Go" />
<input type="hidden" name="check_keywords" value="yes" />
<input type="hidden" name="area" value="default" />
</form>
<p class="searchtip" style="font-size: 90%">
Enter search terms or a module, class or function name.
</p>
</div>
<script type="text/javascript">$('#searchbox').show(0);</script>
</div>
</div>
<h3>Last update:</h3>
<p class="topless">Nov 11, 2014</p>
</div>
</div>
<div id="ft">
<div class="nav">
« <a href="git.html" title="The Django source code repository">previous</a>
|
<a href="index.html" title="Django internals" accesskey="U">up</a></div>
</div>
</div>
<div class="clearer"></div>
</div>
</body>
</html>
distrib
>
Fedora
>
20
>
x86_64
>
media
>
updates
>
by-pkgid
>
3732cf025cb346736dec18a159b95d9b
>
files
>
543
