[docs] [PATCH 1/2] scripts/run-docs-build: add for loop when publishing tags/branches
On Thu, Mar 25, 2021 at 07:12:10PM +0100, Nicolas Dechesne wrote:
Use for loop to avoid repeating the same pattern over and over.What about using `git tag -l 3.2*` so that we don't need to maintain the
list of tags?
Or, maybe `git tag --contains <3.1.5 commit hash introducing sphinx doc>
--contains <3.2 commit hash introducing sphinx doc>` so that the
3.1. tags don't need to be added either?
Same mechanism can be used for bitbake git repo I guess.
On Fri, Mar 26, 2021 at 11:08 AM Quentin Schulz <quentin.schulz@...> wrote:
yes, I thought about that too.. I wanted to get a quick fix first to publish 3.1.6 and 3.2.2 which were missing..
on the other hand, we have a larger issue with this. The 'release' information is needed here , but it's also needed on the website (downloads) and it's needed in the switchers.js as well...
So we probably want to take a high level view of the problem. Michael created https://bugzilla.yoctoproject.org/show_bug.cgi?id=14330 to let us think about it.
my idea would be a publish/maintain a yaml file that would represent the database of all our releases and docs, which would be maintained/updated by the release manager, it would include all information we need to build and publish the docs, update the 'download' page on the website, ...
up until now, we have been using:
i think we need a few improvements to that..