[Django] #21394: Django 1.6 offline docs are actually 1.5.4

[Django]

#21394: Django 1.6 offline docs are actually 1.5.4
-------------------------------+--------------------
Reporter: anonymous | Owner: nobody
Type: Bug | Status: new
Component: Documentation | Version: 1.6
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------+--------------------
The archive at https://docs.djangoproject.com/m/docs/django-
docs-1.6-en.zip contains the docs for Django 1.5.4, instead of Django 1.6

--
Ticket URL: <https://code.djangoproject.com/ticket/21394>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

[Django]

#21394: Django 1.6 offline docs are actually 1.5.4

-------------------------------+------------------------------------

Reporter: anonymous | Owner: nobody
Type: Bug | Status: new
Component: Documentation | Version: 1.6

Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0

Easy pickings: 1 | UI/UX: 0

-------------------------------+------------------------------------
Changes (by claudep):

* needs_better_patch: => 0
* needs_docs: => 0
* needs_tests: => 0
* stage: Unreviewed => Accepted

Comment:

As I can see, this is not a problem with the documentation version itself,
but simply with the version number in the title. It might be caused by the
way the `release` variable is defined in `docs/conf.py`.

--
Ticket URL: <https://code.djangoproject.com/ticket/21394#comment:1>

[Django]

#21394: Django 1.6 offline docs are actually 1.5.4

-------------------------------+-------------------------------------
Reporter: anonymous | Owner: nobody
Type: Bug | Status: closed
Component: Documentation | Version: 1.6
Severity: Normal | Resolution: duplicate

Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0

Needs tests: 0 | Patch needs improvement: 0

Easy pickings: 1 | UI/UX: 0

-------------------------------+-------------------------------------
Changes (by timo):

* status: new => closed
* resolution: => duplicate

Comment:

Duplicate of #21400 (which describes the problem a bit better).

--
Ticket URL: <https://code.djangoproject.com/ticket/21394#comment:2>