Overview
Angel already started a threa for this in Zulip: https://linuxfoundation.zulipchat.com/#narrow/channel/532985-neonephos-platform-mesh-discussion/topic/Bugfix.2Fpatch.20release/with/606222937
I have a kube-like release structure in mind that keeps parity with our currently released artifacts with their own versioning.
To support chunking changes into one build instead of multiple triggers fighting over who gets to build the next aggregate.
Release branches to backport fixes.
I'm thinking of combining this with the migration to ocm v2: platform-mesh/helm-charts#2059
Since we have to migrate anyway it would be a good opportunity.
So the new release structure could be implemented in parallel without touching the v1 release machinery until the v2 works reliably.
Implementation Details
No response
Completion Checklist
Overview
Angel already started a threa for this in Zulip: https://linuxfoundation.zulipchat.com/#narrow/channel/532985-neonephos-platform-mesh-discussion/topic/Bugfix.2Fpatch.20release/with/606222937
I have a kube-like release structure in mind that keeps parity with our currently released artifacts with their own versioning.
To support chunking changes into one build instead of multiple triggers fighting over who gets to build the next aggregate.
Release branches to backport fixes.
I'm thinking of combining this with the migration to ocm v2: platform-mesh/helm-charts#2059
Since we have to migrate anyway it would be a good opportunity.
So the new release structure could be implemented in parallel without touching the v1 release machinery until the v2 works reliably.
Implementation Details
No response
Completion Checklist