docs: Cleanup version histories

[phlax]

Signed-off-by: Ryan Northey [email protected]

Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue] Fix #20963
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

[phlax]

docs rendered here: https://storage.googleapis.com/envoy-pr/20961/docs/index.html

[phlax]

this will conflict with #20958

/wait

[phlax]

/retest

[repokitteh-read-only]

Retrying Azure Pipelines:
Check envoy-presubmit isn't fully completed, but will still attempt retrying.
Retried failed jobs in: envoy-presubmit

🐱

Caused by: a #20961 (comment) was created by @phlax.

see: more, trace.

[phlax]

/retest

[repokitteh-read-only]

Retrying Azure Pipelines:
Retried failed jobs in: envoy-presubmit

🐱

Caused by: a #20961 (comment) was created by @phlax.

see: more, trace.

[alyssawilk]

should we have a step in the release which adds these prefixes? right now we just copy current to version.number.rst

[phlax]

should we have a step in the release which adds these prefixes? right now we just copy current to version.number.rst

probably yes

rst is not the easiest thing to parse and replace with, i think its doable but not trivial

[alyssawilk]

eh, even if we say "do it manually" it's better than you doing it every few months. cc @RyanTheOptimist who can maybe include it when he moves things from governance to releases

[phlax]

even if we say "do it manually"

ah yep, my brain is just in what-can-be-automated mode

[phlax]

should we have a step in the release which adds these prefixes?

following up on this - it needs to happen at the correct time and for the correct docs...

i have posted a lengthier description of the current steps that are afaict required here #20851 (comment)