Release Beta API version

kubernetes-sigs / cluster-api-addon-provider-helm

CAAPH uses Helm charts to manage the installation and lifecycle of Cluster API add-ons.

Apache License 2.0

124 stars 32 forks source link

Release Beta API version #160

Open dtzar opened 9 months ago

dtzar commented 9 months ago

User Story

Move from alpha to beta API version, working towards GA stability with the addon provider.

/kind feature

### Tasks
- [ ] https://github.com/kubernetes-sigs/cluster-api-addon-provider-helm/issues/186
- [ ] https://github.com/kubernetes-sigs/cluster-api-addon-provider-helm/issues/197
- [ ] https://github.com/kubernetes-sigs/cluster-api-addon-provider-helm/issues/196
- [ ] https://github.com/kubernetes-sigs/cluster-api-addon-provider-helm/issues/199
- [ ] https://github.com/kubernetes-sigs/cluster-api-addon-provider-helm/issues/65

Jont828 commented 9 months ago

Did you have any criteria in mind for a beta API version? I know we talked about implementing e2e tests for a beta release tag but not the API version

dtzar commented 8 months ago

I like the thinking in this proposal of having just "experimental" and "stable" channels where beta would be a part of the GA channel.
https://docs.google.com/document/d/1uZEhliv1SoQQIi2c6Wmz_n5wYMjwE9Eyr5-mW7OFDYU/edit?usp=sharing

We would merge the existing beta and GA graduation criteria into a single unified set of requirements:

Full conformance test coverage.
Multiple conformant implementations.
Widespread implementation and usage.
At least 6 months of soak time as an alpha API.
No significant changes for at least 1 minor release and 3 months
Approval from subproject owners + KEP reviewers.

Jont828 commented 8 months ago

I think that makes sense. So under that proposal, would we cut a stable release soon and keep a series of alpha/exp releases that run ahead of it?

k8s-triage-robot commented 5 months ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue as fresh with /remove-lifecycle stale
Close this issue with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

dtzar commented 5 months ago

/remove-lifecycle stale

dtzar commented 2 months ago

I believe the task list just created now is the criteria for a beta release.
There is no ETA on a beta timeline. Contributions welcome!

We would like to have releases ~ every 2 months (even if just dep updates).