RTD Allow projects to change their default-version 73/62373/25
authorAric Gardner <agardner@linuxfoundation.org>
Thu, 21 Nov 2019 21:32:18 +0000 (16:32 -0500)
committerAric Gardner <agardner@linuxfoundation.org>
Mon, 16 Dec 2019 17:23:19 +0000 (12:23 -0500)
commit026509df164f628deb0f4660a172cca364ff58ae
tree261c2de561972e632dada73513f1dc8f7ac9ff26
parent7821ed87b31368d1ced8dbfede6adc58dd64cb15
RTD Allow projects to change their default-version

Allow docs release via jjb config
Changes the default landing page from /latest/ to /stable/

by default we se to /latest/ (a no-op)
And on release change to stable via jjb config.

read the docs, by design creates /latest/ and /stable/ landing points
for the user.

If read the docs sees a tag or a new branch, it creates a /stable/
directory, which follows the latest tag or if there is no tag, the
latest branch.

Related issue where I ask for clarification as to their default
behavior in this regards.
https://github.com/readthedocs/readthedocs.org/issues/6415

ISSUE: RELENG-2549
Signed-off-by: Aric Gardner <agardner@linuxfoundation.org>
Change-Id: I33a8df14e68340ba268c953a471daa02ee6fe766
docs/jjb/lf-rtdv3-jobs.rst
jjb/lf-macros.yaml
jjb/lf-rtdv3-jobs.yaml
releasenotes/notes/lf-rtdv3-jobs-b89edbf358caf261.yaml [new file with mode: 0644]
shell/rtdv3.sh