public inbox for docs@lists.yoctoproject.org
 help / color / mirror / Atom feed
From: "Antonin Godard" <antonin.godard@bootlin.com>
To: "Quentin Schulz" <quentin.schulz@cherry.de>,
	<docs@lists.yoctoproject.org>
Cc: "Michael Opdenacker" <michael.opdenacker@rootcommit.com>,
	"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>
Subject: Re: [PATCH v3 1/2] ref-manual: release-process: update releases.svg
Date: Tue, 29 Oct 2024 14:17:54 +0100	[thread overview]
Message-ID: <D58BI4DHQBK8.3QCYVPUDRH27V@bootlin.com> (raw)
In-Reply-To: <f2a380a0-6dd9-4d6e-9506-0d98d233ad06@cherry.de>

On Tue Oct 29, 2024 at 11:57 AM CET, Quentin Schulz wrote:
[...]
>> So perhaps:
>>
>> - Add a date stamp after "Current".
>> - Automate the deployment of the svg file, like what's done for the migration
>>    manuals.
>> - Mention the documentation's release above the graph with &DISTRO_NAME.
>>
>
> 1) and 3) should be rather straightforward I hope. For 3) you could
> maybe just use Sphinx captions for example.
>
> 2) would need to happen in the autobuilder script for building the docs.
> If I remember correctly, I adapted the script so it can run locally too
> so you don't necessarily have to use the autobuilder.
> https://git.yoctoproject.org/yocto-autobuilder-helper/tree/scripts/run-docs-build.
> mmmmmm I think the supported release manuals entry is actually
> autogenerated by set_versions.py. I think you would want to add the svg
> (and the text somehow?) to this line
> https://git.yoctoproject.org/yocto-autobuilder-helper/tree/scripts/run-docs-build#n151
> ?
> It seems more involved than 1 and 3 for now so maybe more time consuming.
>
>> Is the best we can do?
>>
>
> It's a start for now, maybe we'll have more ideas in the future :)

Thanks for the pointers! I'll probably send some patches this week…

> Cheers,
> Quentin

Cheers,
Antonin

--
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


  reply	other threads:[~2024-10-29 13:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-23  7:32 [PATCH v3 0/2] ref-manual: release process: update LTS section Antonin Godard
2024-10-23  7:32 ` [PATCH v3 1/2] ref-manual: release-process: update releases.svg Antonin Godard
2024-10-28 10:40   ` Quentin Schulz
2024-10-28 13:53     ` Antonin Godard
2024-10-28 14:33       ` Quentin Schulz
2024-10-29  9:26         ` Antonin Godard
2024-10-29 10:57           ` Quentin Schulz
2024-10-29 13:17             ` Antonin Godard [this message]
2024-10-23  7:32 ` [PATCH v3 2/2] ref-manual: release-process: refresh the current LTS releases 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=D58BI4DHQBK8.3QCYVPUDRH27V@bootlin.com \
    --to=antonin.godard@bootlin.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=michael.opdenacker@rootcommit.com \
    --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