Generation of Release Page

[MrBatschner]

What would you like to be added:

The Garden Linux release page should be created automatically. This used to be a (semi-) automatic step with previous Garden Linux releases (i.e. 576) but with the change to the new release process involving GitHub actions, this process is broken.

Things that need a bit of work:

• Tagging the code: There are beta_XXX tags in the Garden Linux repository which contain all build logs, binary artefacts and test results. Once Garden Linux gets release to the cloud providers, this tag should be renamed to just XXX (drop the `beta_´ prefix) without loosing all release artefacts.
• Component descriptor: once released, the component descriptor should be attached to the release artefacts.
• Automated in release step: since this step used to be semi-automatic, it should be fully automatic inside the promote-gardenlinux-task.

Why is this needed:

Releasing Garden Linux 934.0 and 934.1 revealed major problems with the release page. While the release page for Garden Linux 934.1 could be assembled manually with great effort, the release page for Garden Linux 934.0 is still missing and relevant information was not even made available.

[MrBatschner]

Like before with Garden Linux 576, the release page should contain the component descriptor.

[ccwienk]

@MrBatschner : I think we need to align on where to create gh-release. should it be the original gardenlinux-repository, or this one?

[MrBatschner]

@MrBatschner : I think we need to align on where to create gh-release. should it be the original gardenlinux-repository, or this one?

Yes, in the original Garden Linux repo.

[ccwienk]

okay, I shall work in sth.