Allow for stable to be on a rolling release.

[Daltz333]

So I have an interesting problem.

My project (frc-docs) has a stable release (2020 tag) that is based yearly, as an archival system. We want users to view the year specific documentation as don't want them to accidentally view documentation for features that are now available yet. Here comes the tricky part. Starting in November is when we make those features live. I'd like to be able to push a commit, and have that change live on stable without having to create a tag. Currently switching between latest and stable breaks links for websites and users.

Suggestions are welcome

[stsewd]

Not sure If I understood this completely.

You have docs.com/en/2020 (stable points to it), and you also have master (latest points to master). Now in november, you want to stable point to master?

We are also planning into have more flexibility in marking other versions as stable/latest #5319

[Daltz333]

Yep!

[stsewd]

So, to what version would latest point to after that?

[Daltz333]

latest would likely be unused until when we archive the next release (2021)

• November (switch from latest to stable as rolling releases)
• May (stable is fixed to our yearly tag, latest is now rolling releases)

Where stable is the default prefix. We just don't want to constantly be switching from
https://docs.wpilib.org/en/stable
https://docs.wpilib.org/en/latest

[Daltz333]

@stsewd I think a potential implementation would be for automation rules to be applied to commits.

Have a commit update/activate a specific version on RTD.

Then it would be easy to

• Match: Any Commit
• Version Type: Existing Version
• Version: Stable
• Action: Update

[stsewd]

Don't think we may want to add automation rules for commits (at least for now), but when we have the feature for marking any version as stable, it would likely be added in the api v3, so you can make use of that (and the option will be available from the dashboard as well).

Another solution, but not sure if works for you, is to create a branch named stable, this will remove the rtd's stable, but still sort that version like it does with stable IIRC

[Daltz333]

Hm. Its less than perfect, but it'll due for now. I'd like to keep this issue open as a feature request.