From: Michael Opdenacker <michael.opdenacker@rootcommit.com>
To: Antonin Godard <antonin.godard@bootlin.com>, docs@lists.yoctoproject.org
Cc: michael.opdenacker@rootcommit.com,
Quentin Schulz <quentin.schulz@cherry.de>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [PATCH v2 0/2] ref-manual: release process: update LTS section
Date: Tue, 22 Oct 2024 16:13:49 +0000 (UTC) [thread overview]
Message-ID: <7e5d389b-cee8-4e90-9133-0d4ff50ca5d4@rootcommit.com> (raw)
In-Reply-To: <D52B130IVLTK.28FJTB79L17DQ@bootlin.com>
On 10/22/24 13:39, Antonin Godard wrote:
> On Tue Oct 22, 2024 at 1:03 PM CEST, Antonin Godard wrote:
>> Update the releases.svg file. Link to preview:
>> https://lufi.bootlin.com/r/VXPQ7d5NDt#kPjQDABd0EORG6GJCMG2U0IdU1+tGuUMHvWk8GofBsM=
> Realizing I wrote "Current" instead of "Long Term Support" in the diagram. I will
> fix that.
Actually, "Current" looks good to me as "LTS" already appears next to
the release name.
Now that Styhead has been released, you should also change its color to
"Current", the same color as for Scarthgap.
Thanks
Michael.
--
Michael Opdenacker
Root Commit
Embedded Linux Training and Consulting
https://rootcommit.com/
next prev parent reply other threads:[~2024-10-22 16:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-22 11:03 [PATCH v2 0/2] ref-manual: release process: update LTS section Antonin Godard
2024-10-22 11:03 ` [PATCH v2 1/2] ref-manual: release-process: update releases.svg Antonin Godard
2024-10-22 11:03 ` [PATCH v2 2/2] ref-manual: release-process: refresh the current LTS releases Antonin Godard
2024-10-22 16:17 ` Michael Opdenacker
2024-10-22 11:39 ` [PATCH v2 0/2] ref-manual: release process: update LTS section Antonin Godard
2024-10-22 16:13 ` Michael Opdenacker [this message]
2024-10-23 7:17 ` Antonin Godard
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=7e5d389b-cee8-4e90-9133-0d4ff50ca5d4@rootcommit.com \
--to=michael.opdenacker@rootcommit.com \
--cc=antonin.godard@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--cc=quentin.schulz@cherry.de \
--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