[ckan-dev] Readthedocs and CKAN documentation versions

[Sean Hammond]

> If we are to create private branches anyway why don't we create the
> docs from the release branch, ie  docs.ckan.org/en/release-v2.0 as
> private, which will keep updated and create the tag based ones on
> release as have been doing until now?

Because we want the public to be able to access the release-v2.1 (beta)
docs, for example, as soon as release-v2.1 has been branched. So I want
the release-v* branches to be built publicly and shown in the versions
links in the bottom right, instead of the ckan-* tags.