Re: [PATCH v3 1/2] ref-manual: release-process: update releases.svg

[Quentin Schulz <quentin.schulz@cherry.de>]

Hi Antonin,

On 10/23/24 9:32 AM, Antonin Godard wrote:
> * Add Walnascar release.
> * Remove dunfell, gatesgarth, hardknott, honister: these release are not
>    supported anymore. Start from kirkstone, which is still supported.
> 
> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
> ---
>   documentation/ref-manual/svg/releases.svg | 907 ++++++++++++------------------
>   1 file changed, 346 insertions(+), 561 deletions(-)
> 
> diff --git a/documentation/ref-manual/svg/releases.svg b/documentation/ref-manual/svg/releases.svg
> index 036aa467cc2e646e99bc407bbf0ea7ff8825f57b..b1036e066ceb65a7391cec616cb4304094728f3f 100644
> --- a/documentation/ref-manual/svg/releases.svg
> +++ b/documentation/ref-manual/svg/releases.svg
> @@ -2,11 +2,14 @@
[...]
> +    <text
> +       xml:space="preserve"
> +       style="font-weight:bold;font-size:13.3333px;line-height:125%;font-family:'Nimbus Roman';-inkscape-font-specification:'Nimbus Roman, Bold';letter-spacing:0px;word-spacing:0px;writing-mode:lr-tb;fill:#fffefe;fill-opacity:1;stroke:#000000;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1"
> +       x="1659.087"
> +       y="-3.6722763"
> +       id="text1185-3-55-4-0-0-0-1-1-6-4-3-5-2-2"><tspan
> +         sodipodi:role="line"
> +         x="1659.087"
> +         y="-3.6722763"
> +         style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:13.3333px;font-family:'Liberation Sans';-inkscape-font-specification:'Liberation Sans';text-align:center;text-anchor:middle;fill:#000000;fill-opacity:1;stroke:none"
> +         id="tspan10317-2-9-1-4-6-5-6-6-5-9-7">Current</tspan></text>

This is a bit dangerous as "current" keeps its meaning while time 
passes. So building docs from years ago from a tarball will still say 
"current" event though it isn't really supported anymore. The X axis 
showing the dates should be enough for people to get the idea, but maybe 
we can also add the last update date of the SVG after Current? e.g. 
"Current (Oct. 2024)"?

Additionally updating that SVG for all releases might be an issue. If we 
backport it "too far" then the release of the docs will not even be in 
that graph anymore, which is a bit odd. Moreover, the paragraph in the 
LTS section may become outdated as well.

A random thought I just had was to maybe treat this the same way we do 
with the migration manuals, that is to take the source from the last 
release/master and inject it into all earlier releases whenever we build 
the docs through the autobuilder. We could still have an outdated 
version if people build it from an old tarball but there's no much we 
can do about that sadly.

What do you think?

Cheers,
Quentin