Yuri Shkuro

(side note - we also need to upgrade the backend release process to make v2 the primary version)

release.sh in the docs is what makes the release - it creates a snapshot of next-release dir into a numbered dir and does some config manipulation plus some url rewriting...

You can see the release process described in RELEASE.md (backend, ui, and docs repos have it)

> I get the impression that you put out a release every month, some time during the first week of the month? Is that correct? That is correct, we release...

> Ideally, we shouldn't have any config for the versions in hugo.yaml Yes, there's no strong reason to have them hardcoded, they can all be computed. But the versions in...

@chalin does docsy have a blessed / recommended way of managing versions? We could adopt it if necessary. It was my understanding it supports either sub-directories (what we already use)...

I fixed it for the current website ff40c08. The page itself logically is an Introduction. I don't think the left menu requires "2.6" root - we're not going to have...

do you have an example of "default" way docsy does versioning? I see that k8s does it via subdomains.

But it doesn't answer my question since it seems we need to make a directional decision about the files organization in order for you to progress with docsy prototype. At...

Repro https://github.com/jaegertracing/jaeger/issues/7346