Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release Beta API version #160

Open
5 tasks
dtzar opened this issue Jan 29, 2024 · 6 comments
Open
5 tasks

Release Beta API version #160

dtzar opened this issue Jan 29, 2024 · 6 comments
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@dtzar
Copy link
Contributor

dtzar commented Jan 29, 2024

User Story

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

/kind feature

Tasks

  1. kind/bug lifecycle/rotten
    mboersma
  2. kind/bug
    mboersma
  3. kind/bug lifecycle/rotten
  4. kind/bug
  5. kind/feature
@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Jan 29, 2024
@Jont828
Copy link
Contributor

Jont828 commented Feb 5, 2024

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

@Jont828 Jont828 self-assigned this Feb 12, 2024
@dtzar
Copy link
Contributor Author

dtzar commented Feb 13, 2024

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
Copy link
Contributor

Jont828 commented Feb 21, 2024

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
Copy link

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 22, 2024
@dtzar
Copy link
Contributor Author

dtzar commented May 22, 2024

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 22, 2024
@dtzar
Copy link
Contributor Author

dtzar commented Aug 12, 2024

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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

4 participants