Closed harrislapiroff closed 10 years ago
I don't think this is a problem. The latest version is the latest version, not a release.
I think it is a probably because I was trying to make sure RTD was building correctly when I realized I had no way to verify that what RTD called "latest" was version 2.1.2. And there's no alternative link to 2.1.2, so as far as a user is concerned, documentation for 2.1.2 doesn't exist.
On Fri, Sep 5, 2014 at 6:24 PM, Stephen Burrows notifications@github.com wrote:
I don't think this is a problem. The latest version is the latest version, not a release.
Reply to this email directly or view it on GitHub: https://github.com/littleweaver/django-daguerre/issues/61#issuecomment-54689221
Could just be a problem with our RTD build settings though. There probably should be a link.
On Fri, Sep 5, 2014 at 6:26 PM, Harris Lapiroff harris@chromamine.com wrote:
I think it is a probably because I was trying to make sure RTD was building correctly when I realized I had no way to verify that what RTD called "latest" was version 2.1.2. And there's no alternative link to 2.1.2, so as far as a user is concerned, documentation for 2.1.2 doesn't exist. On Fri, Sep 5, 2014 at 6:24 PM, Stephen Burrows notifications@github.com wrote:
I don't think this is a problem. The latest version is the latest version, not a release.
Reply to this email directly or view it on GitHub: https://github.com/littleweaver/django-daguerre/issues/61#issuecomment-54689221
Yeah, we should just be building 2.1.2 and latest separately.
Set up separate 2.1.2 build.
Which is actually a problem, since RTD just refers to it as "latest".