public inbox for docs@lists.yoctoproject.org
 help / color / mirror / Atom feed
From: Quentin Schulz <quentin.schulz@cherry.de>
To: antonin.godard@bootlin.com, docs@lists.yoctoproject.org
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [docs] [PATCH] ref-manual: update releases.svg
Date: Fri, 18 Oct 2024 13:53:47 +0200	[thread overview]
Message-ID: <82a4e314-cedc-4cb4-a8a9-bc3fd3e81c94@cherry.de> (raw)
In-Reply-To: <20241018-update-releases-svg-v1-1-502899b5d780@bootlin.com>

Hi Antonin,

On 10/18/24 1:38 PM, Antonin Godard via lists.yoctoproject.org wrote:
> * Add Walnascar release.
> * Remove dunfell, gatesgarth, hardknott, honister: these release are not
>    supported anymore. Start from kirkstone, which is still supported.
> 

I think we also need to update the paragraph where this appears.

Indeed, we're missing the information that Scarthgap is the latest LTS 
and is supported until 2028 (it's in the SVG though, so maybe that's 
enough?).

I would keep the releases that are unmaintained but newer than the last 
LTS. The issue is that Styhead (and Walnascar) is going to be EoL before 
Scarthgap, so are we going to update the SVG in Scarthgap when Styhead 
is EoL? If not, then we'd be inconsistent with what we've done for 
Kirkstone for example.

Just trying to figure out what's the plan here so we can stick to it :)

It'd be nice if you have the SVG published somewhere so we can see it 
without applying the patch locally, is this something you could do to 
make reviewing easier?

Cheers,
Quentin


  reply	other threads:[~2024-10-18 11:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-18 11:38 [PATCH] ref-manual: update releases.svg Antonin Godard
2024-10-18 11:53 ` Quentin Schulz [this message]
2024-10-18 14:01   ` [docs] " Michael Opdenacker
2024-10-22  9:16     ` Antonin Godard
  -- strict thread matches above, loose matches on Subject: below --
2024-04-30 21:27 michael.opdenacker
2024-05-03 15:11 ` [docs] " Quentin Schulz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=82a4e314-cedc-4cb4-a8a9-bc3fd3e81c94@cherry.de \
    --to=quentin.schulz@cherry.de \
    --cc=antonin.godard@bootlin.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=thomas.petazzoni@bootlin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox