Docs for older mongoengine releases are not visible on Read the Docs

[bmbouter]

We use mongoengine 0.7.10, and I'm constantly reading the docs from github directly instead of reading the on Read the Docs. The Read the Docs site only shows 'latest'. I think that previous releases or release streams should be versioned in Read the Docs. Just enable builders in RTD config for the release branch or each tagged release. I think doing the release branches is probably the best thing to do.

[amcgregor]

Interesting issue.

Of course, upgrading is significantly worth it and support can only really be offered on the current stable version. Having multi-versioned documentation only really makes sense when you actually have multiple stable branches a la Python 2 and 3.

For your case, simply checking out a copy of the code for the version you are using, then building the documentation locally, once, should be more than sufficient.

[mmellison]

@amcgregor IMO multi-versioned documentation makes sense. I work in a shop where we are not allowed to arbitrarily upgrade our third party repositories, so we may be using third party software that is two or three releases behind. In this case, we have sometimes created our own internal RTD instance building documentation for third party projects.

Yes, you can compile the documentation directly but since RTD already supports version documentation it would be nice to see them built.

[bmbouter]

We are also not in a position to arbitrarily upgrade our third part dependencies like mongoengine. We use 0.7.10 because it's what is available on RHEL 6.0. Also we have 10+ developers so everyone independently building a specific version of docs isn't very efficient.

I think having docs for two or three releases behind would benefit our usage of mongoengine. It's also so easy to turn on; it's literally a few clicks.