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

TEP-0114: Remove the feature flag custom-task-version in release v0.47.0 #5837

Closed
Tracked by #5863
XinruZhang opened this issue Dec 5, 2022 · 5 comments · Fixed by #6499
Closed
Tracked by #5863

TEP-0114: Remove the feature flag custom-task-version in release v0.47.0 #5837

XinruZhang opened this issue Dec 5, 2022 · 5 comments · Fixed by #6499
Assignees
Labels
kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@XinruZhang
Copy link
Member

XinruZhang commented Dec 5, 2022

Remove the feature flag custom-task-version in release v0.47.0, which means we stop supporting v1alpha1.Run anymore.

Background

As proposed in TEP-0114, the default value of custom-task-version is set to v1alpha1 in the first release, approximately v0.43.0, then we switch it to v1beta1 in v0.44.0 (which is tracked by #5836), then eventually remove it in release v0.47.0.

cc @jerop @abayer

@tekton-robot tekton-robot added the kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API label Dec 5, 2022
@jerop jerop changed the title Remove the feature flag custom-task-version in release v0.47.0 TEP-0114: Remove the feature flag custom-task-version in release v0.47.0 Dec 10, 2022
@jerop jerop added this to the Pipelines v0.47 milestone Dec 13, 2022
@tekton-robot
Copy link
Collaborator

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle stale

Send feedback to tektoncd/plumbing.

@tekton-robot tekton-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 13, 2023
@vdemeester
Copy link
Member

/lifecycle frozen

@tekton-robot tekton-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Mar 13, 2023
@pritidesai
Copy link
Member

@XinruZhang any updates on this one?

@XinruZhang
Copy link
Member Author

Thank you @pritidesai, yes this is on my plate for this release :)

@Yongxuanzhang
Copy link
Member

/assign

Yongxuanzhang added a commit to Yongxuanzhang/pipeline that referenced this issue Apr 5, 2023
This commit closes tektoncd#5837. It removes the feature flag
custom-task-version to stop supporting v1alpha1.Run as planed in
TEP-114. There will be a separate PR to remove the v1alpha1.Run tracking
by tektoncd#6498.

Signed-off-by: Yongxuan Zhang yongxuanzhang@google.com
Yongxuanzhang added a commit to Yongxuanzhang/pipeline that referenced this issue Apr 5, 2023
This commit closes tektoncd#5837. It removes the feature flag
custom-task-version to stop supporting v1alpha1.Run as planed in
TEP-114. There will be a separate PR to remove the v1alpha1.Run tracking
by tektoncd#6498.

Signed-off-by: Yongxuan Zhang yongxuanzhang@google.com
Yongxuanzhang added a commit to Yongxuanzhang/pipeline that referenced this issue Apr 5, 2023
This commit closes tektoncd#5837. It removes the feature flag
custom-task-version to stop supporting v1alpha1.Run as planed in
TEP-114. There will be a separate PR to remove the v1alpha1.Run tracking
by tektoncd#6498.

Signed-off-by: Yongxuan Zhang yongxuanzhang@google.com
Yongxuanzhang added a commit to Yongxuanzhang/pipeline that referenced this issue Apr 5, 2023
This commit closes tektoncd#5837. It removes the feature flag
custom-task-version to stop supporting v1alpha1.Run as planed in
TEP-114. There will be a separate PR to remove the v1alpha1.Run tracking
by tektoncd#6498.

Signed-off-by: Yongxuan Zhang yongxuanzhang@google.com
Yongxuanzhang added a commit to Yongxuanzhang/pipeline that referenced this issue Apr 5, 2023
This commit closes tektoncd#5837. It removes the feature flag
custom-task-version to stop supporting v1alpha1.Run as planed in
TEP-114. There will be a separate PR to remove the v1alpha1.Run tracking
by tektoncd#6498.

Signed-off-by: Yongxuan Zhang yongxuanzhang@google.com
Yongxuanzhang added a commit to Yongxuanzhang/pipeline that referenced this issue Apr 6, 2023
This commit closes tektoncd#5837. It removes the feature flag
custom-task-version to stop supporting v1alpha1.Run as planed in
TEP-114. There will be a separate PR to remove the v1alpha1.Run tracking
by tektoncd#6498.

Signed-off-by: Yongxuan Zhang yongxuanzhang@google.com
tekton-robot pushed a commit that referenced this issue Apr 6, 2023
This commit closes #5837. It removes the feature flag
custom-task-version to stop supporting v1alpha1.Run as planed in
TEP-114. There will be a separate PR to remove the v1alpha1.Run tracking
by #6498.

Signed-off-by: Yongxuan Zhang yongxuanzhang@google.com
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
Status: Done
6 participants