Setup the build process for the complete "MCP Landscape Component"

[In-Ko]

Description
openMCP is a rich software Component consisting of many subcomponents. We call this overarching component the "MCP Landscape Component". Admins running this openMCP stack in their own orgs needs to be aware of features/changes/necessary migrations etc. which are coming with each new MCP Landscape Component Release.

So it is required that during generation of a new openMCP Release, a consistent Release Note is created, based on the new releases of each individual MCP Component.

Done Criteria

• Provide one shared openMCP Release in public org
• One openMCP release aggregates a set bundle of subcomponents in a fixed version
• The release notes are at least semi/automated, from Git Commit messages, verified by person releasing

Out of scope for now

• Automate announcement using email/fax/slack or anything else
• Persist, replicate to our documentation pages

[moelsayed]

As a prerequisite for this, I am working on moving all the components to use the common Taskfile build script:

• chore: Use shared Task definitions project-workspace-operator#36
• chore: Use shared Task definitions control-plane-operator#40
• chore: Use shared Task definitions quota-operator#26

[moelsayed]

following up on getting a repo for this https://github.tools.sap/OSS-Outbound-Process/openmcp-project-openmcp-repo/issues/3

[moelsayed]

Currently working on trying to figure out how to build an openMCP bundle using ocm.

[moelsayed]

The first iteration of the build and release process for the MCP Landscape components is done. I would like to get a review from as many people as possible.

The current openmcp repo has the following files:

• component-constructor.yaml: this contains an ocm component constructor for the MCP Landscape. It currently references all the open-sourced components I published as a show case, We can add the reset later once we agree on the process. I really need review on this one!
• components-versions.yaml: is a very simple file for setting up the current components versions associated with the current MCP Landscape release.
• VERSION: the MCP Landscape current released version.
• release.yaml: the github action for the build and publish process. including generating the aggregated release notes.
  To cut a new release you need to do the following steps:
• Make sure components-versions.yaml is up to date with compatible versions.
• Create a PR to bump VERSION file
• In the PR body, write some highlights related to this release. This will be included in the generated in the aggregated release notes.
• Merge the release PR.
• A draft release will be automatically created, this draft should be reviewed as it contains generated content, and then published.

A sample release can be found here.
Follow up issues:

• The templates for release-notes in other components could use some tweaking to look better, I added some workarounds to help with that but it really should be cleaned up upstream.
• The repo still needs some work to be open-source-ready, but it's not a blocker, just a few copy/pasted files.
• I didn't use the build repo taskfiles for this, yet, just to get something working quickly. I will as soon as we agree on the workflow.