Suricata

Perhaps useful and worth a try to look at: https://michaelgoerz.net/notes/showing-a-warning-for-the-latest-documentation-on-readthedocs/index.html

Through experimentation, and confirmation from RTD support, tags must be parseable semantic versions for this to work. Our tag scheme, suricata-x.y.z is not due to the prefixing before the version.

Others have run into this issue as well and there is an open ticket for a feature that may help those with tags that aren't exactly semver: https://github.com/readthedocs/readthedocs.org/issues/5318

How do we feel about this?
The ticket that could help is still open...

Juliana Fajardini Reichow wrote in #note-11:

How do we feel about this?
The ticket that could help is still open...

This is still an issue. It would be nice to fix sooner than the 9.0 cycle though, as it does lead to confusion.. And will again after master and 8.0 diverge.

So do we come up with some sort of workaround, since a more automated way isn't possible yet?

Juliana Fajardini Reichow wrote in #note-13:

So do we come up with some sort of workaround, since a more automated way isn't possible yet?

I don't know what it would be, but even without a work-around or possible one, its a known issue. So the ticket can stay open I think.

One possible option I suppose is a shadow-repo that follows tags that RTD expects. By that I mean, just another Suricata repo that exists purely for documentation. Seems like a bad hack though.

Jason Ish wrote in #note-14:

I don't know what it would be, but even without a work-around or possible one, its a known issue. So the ticket can stay open I think.

okie

One possible option I suppose is a shadow-repo that follows tags that RTD expects. By that I mean, just another Suricata repo that exists purely for documentation. Seems like a bad hack though.

indeed...