I'm still unclear on whether you'd want A or B: A) Different major/minor versions of the spec are different documents B) Different versions of the spec are tags or branches of the same document
If it's B, then you'd either: 1) only build the latest version, and construct an index of links to the unrendered old versions in vcs history 2) use a custom build/publishing worflow that pulls versions out of history so they can be built as peers in the published version On Sun, Sep 6, 2015 at 9:26 PM, Nick Coghlan <ncogh...@gmail.com> wrote: > On 7 September 2015 at 14:11, Marcus Smith <qwc...@gmail.com> wrote: > > > > > >> > That way, the URL works as people expect, *and* the resulting > >> > destination gives a URL that (when inevitably copy-and-pasted) will > >> > retain its meaning over time. > >> > >> Yes, ReadTheDocs does let us do that. > > > > > > well, it lets you do it for a whole project. > > RTD also has page redirects now: > > https://read-the-docs.readthedocs.org/en/latest/user-defined-redirects.html#page-redirects > (I thought the same thing you did, but found that when double > checking) > > So we *could* redirect unqualified links to qualified ones if we > wanted to. I just don't want to :) > > Cheers, > Nick. > > -- > Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia >
_______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
