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

Update API compatibility policy for V1/GA #5633

Closed
dibyom opened this issue Oct 11, 2022 · 1 comment · Fixed by #5634
Closed

Update API compatibility policy for V1/GA #5633

dibyom opened this issue Oct 11, 2022 · 1 comment · Fixed by #5634
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@dibyom
Copy link
Member

dibyom commented Oct 11, 2022

Feature request

Our current policy describes alpha and beta. We need to update it for GA.

Use case

  1. As a Tekton user, I'd like to know what API guarantees Tekton V1 provides
  2. As a Tekton developer, I'd like to know how to experiment with new features post the V1 release.

We had some discussion on this in the API WG and I also wrote up a doc based on my reading of the Kubernetes V1 policies

(join https://groups.google.com/forum/#!forum/tekton-dev for access)

This issue is only for tracking changes/updates to our policy. Development guidelines for post v1 dev work is tracked in #5504 and any potential changes to our feature gates implementation is tracked in #5632

@dibyom dibyom added the kind/feature Categorizes issue or PR as related to a new feature. label Oct 11, 2022
@dibyom dibyom linked a pull request Oct 11, 2022 that will close this issue
7 tasks
@dibyom
Copy link
Member Author

dibyom commented Oct 12, 2022

one open question around beta feature gates in v1 apiVersion: #5628 (comment)

dibyom added a commit to dibyom/pipeline that referenced this issue Oct 17, 2022
This commit describes our API policiy for our GA APIs (e.g. v1). It also
clarifies how TEP-33 Feature Gates interacts with CRD API versions.

Fixes tektoncd#5633

Signed-off-by: Dibyo Mukherjee <dibyo@google.com>
dibyom added a commit to dibyom/pipeline that referenced this issue Oct 24, 2022
This commit describes our API policiy for our GA APIs (e.g. v1). It also
clarifies how TEP-33 Feature Gates interacts with CRD API versions.

Fixes tektoncd#5633

Signed-off-by: Dibyo Mukherjee <dibyo@google.com>
dibyom added a commit to dibyom/pipeline that referenced this issue Nov 10, 2022
This commit describes our API policiy for our GA APIs (e.g. v1). It also
clarifies how TEP-33 Feature Gates interacts with CRD API versions.

Fixes tektoncd#5633

Signed-off-by: Dibyo Mukherjee <dibyo@google.com>
dibyom added a commit to dibyom/pipeline that referenced this issue Nov 11, 2022
This commit describes our API policiy for our GA APIs (e.g. v1). It also
clarifies how TEP-33 Feature Gates interacts with CRD API versions.

Fixes tektoncd#5633

Signed-off-by: Dibyo Mukherjee <dibyo@google.com>
dibyom added a commit to dibyom/pipeline that referenced this issue Nov 18, 2022
This commit describes our API policiy for our GA APIs (e.g. v1). It also
clarifies how TEP-33 Feature Gates interacts with CRD API versions.

Fixes tektoncd#5633

Signed-off-by: Dibyo Mukherjee <dibyo@google.com>
tekton-robot pushed a commit that referenced this issue Nov 18, 2022
This commit describes our API policiy for our GA APIs (e.g. v1). It also
clarifies how TEP-33 Feature Gates interacts with CRD API versions.

Fixes #5633

Signed-off-by: Dibyo Mukherjee <dibyo@google.com>
Repository owner moved this from Todo to Done in Tekton Community Roadmap Nov 18, 2022
jagathprakash pushed a commit to jagathprakash/pipeline that referenced this issue Nov 29, 2022
This commit describes our API policiy for our GA APIs (e.g. v1). It also
clarifies how TEP-33 Feature Gates interacts with CRD API versions.

Fixes tektoncd#5633

Signed-off-by: Dibyo Mukherjee <dibyo@google.com>
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
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant