Clear Release Expectations

[Rotfuks]

Motivation

We have many components that have regular releases of new versions. For this we have many different release processes throughout the many giantswarm teams - and in some occasions even a different approach to what a release even is.
In order for us to really own and improve the kubernetes lifecycle and new releases, we first have to understand and define a common approach and vocabulary around releases.

Stories

Beta Give feedback

1. Release Definition Investigation #2523
   area/kaas team/turtles +2
   
2. Existing Release Process Investigation #2524
   area/kaas team/turtles +2
   
3. Investigation - How to wrap Bundles: Component Groupings #2525
   area/kaas team/turtles +2
   
4. Investigation - How to wrap Bundles: Bundle Wrapper #2773
   area/kaas team/turtles +2
   
5. Visualise Dependency Graph of proposed Bundles #2866
   area/kaas team/turtles +2
   
6. Investigate App Platform vs. Helm Releases #2867
   area/kaas team/turtles +2
   
7. Create Release Framework Document Draft #2909
   area/kaas team/turtles +2
   

Outcome

Once this epic is done we have a clear definition and model of the current state of our release processes that can be used for further discussions and improvements of the status quo.

Context

• https://github.com/giantswarm/giantswarm/issues/25443

[Rotfuks]

There is already an RFC that touches those topics: giantswarm/rfc#68

[Rotfuks]

Outcome achieved with the documented release framework here: https://intranet.giantswarm.io/docs/product/releases/capi-release-framework/