version[added|changed] directives should understand released versions and unreleased ones.

[Marc Fargas]

There are some ".. versionadded:: development" strings in trunk's documentation.

According to contributing.txt (1) and somehow to a relevant thread(2) those should read: .. versionadded:: 1.1

1: ​contributing.txt
2: ​a revelant thread

[Marc Fargas]

Fixes

[Marc Fargas]

Patch to support the version[added|changed] directive as talked on IRC.

[Marc Fargas]

Attached a patch modifiyng Sphinx behaviour as talked on IRC with Jacob, in brief:

A new config value is added to conf.py called "django_next_version" to tell Sphinx which is the next version we will release.

With this in place, when a version[added|changed] directive has the number of django_next_version it will be replaced by a "Development Version" note, otherwise, two things can happen:

• If the directive has an explanation paragraph it is left *as-is*.
• If there's no additional paragraph a Link to the corresponding release notes is placed on the "Changed/NEw in ...." note.

That allows to remove the informational paragraphs after release removing the clutter on the docs after release.

[Marc Fargas]

Good day to update patches ;)

[Malcolm Tredinnick]

(In [10006]) Fixed #9436 -- Updated docs build code to create "new in development version".
Patch from Marc Fargas.