restrict stable version to tags

[dschult]

We create a tagged version of our github repo for each release. But we also have branches and sometimes the branch name parses to a version more recent than our stable tag. So the branch becomes the "stable" release on readthedocs. It'd be nice to restrict the choice of the "stable" release to only be from the github tags instead of including both tags and branches.

We can of course be very careful how we name our branches. But that choice is rarely done with readthedocs in mind and its a surprise when the stable docs suddenly change because we created a branch in the repository.

Perhaps this is just a github issue, but I suspect it has wider impact too.

[workarounds and other options would be appreciated too]

[kmike]

This issue affects Scrapy: version names in Scrapy docs don't make any sense now. "Latest" points to 1.0, "stable" points to upcoming 1.1 and "master" points to master (upcoming 1.2). So latest is the oldest, and stable is not released yet.

I'm not sure how we got here :) It might be an error on our side, but it is not clear how to fix it.

[humitos]

This logic was implemented at #3331

Please, would you mind confirming if you still have this issue? I think it should have solved now. If the problem is gone, please close the issue :)