[EPIC] - Greenhouse Release Process

[IvoGoman]

Priority

None

Description

As a maintainer of Greenhouse I want to an automatic process to create new releases, so that I don't have manual efforts to create changelog, release artefacts, or pinning versions

Now that the Greenhouse Dashboard is publicly available at https://github.com/cloudoperators/juno it is possible to create a release that contains all parts of Greenhouse.

Acceptance Criteria

• [ ] #592
• [x] #593
• [ ] https://github.com/cloudoperators/documentation/pull/15
• [x] #539
• [ ] #594

Reference Issues

No response

[auhlig]

As per todays workgroup discussion:

• Define and document (codify?) how to do a coherent release of back- and frontend
• Plugins must be independent of the core release.