What would you like to be added:
There should be a fixed release job for the ocm repository that creates a new release. Propose schedule is every 4 weeks, proposed version increment is to increment the minor version.
Why is this needed:
Right now the job is triggered manually. Often we waited for PRs in progress to get as many features into a new version. That lead to a slow release cadence. To have a clear release strategy that we can also communicate, makes it easier for consumers to plan for changes in their OCM (cli) consumption.
What would you like to be added: There should be a fixed release job for the ocm repository that creates a new release. Propose schedule is every 4 weeks, proposed version increment is to increment the minor version.
Why is this needed: Right now the job is triggered manually. Often we waited for PRs in progress to get as many features into a new version. That lead to a slow release cadence. To have a clear release strategy that we can also communicate, makes it easier for consumers to plan for changes in their OCM (cli) consumption.