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-0096]: V1 plan for ClusterTask #627

Merged
merged 1 commit into from
Feb 14, 2022
Merged

Conversation

lbernick
Copy link
Member

@lbernick lbernick commented Feb 7, 2022

This commit updates our v1 plan to recommend leaving ClusterTask in beta.
We haven't received any user feedback (on tektoncd/pipeline#4476) indicating that ClusterTasks meet a use case that
isn't met with remote resolution. We should wait to see how remote resolution works for users
before deciding to increase stability guarantees for ClusterTask.

/kind tep

This commit updates our v1 plan to recommend leaving ClusterTask in beta.
We haven't received any user feedback indicating that ClusterTasks meet a use case that
isn't met with remote resolution. We should wait to see how remote resolution works for users
before deciding to increase stability guarantees for ClusterTask.
@tekton-robot tekton-robot added the kind/tep Categorizes issue or PR as related to a TEP (or needs a TEP). label Feb 7, 2022
@tekton-robot tekton-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Feb 7, 2022
@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 7, 2022
Copy link
Member

@pritidesai pritidesai left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sounds good, thank you @lbernick 👍

@tekton-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jerop, pritidesai

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@jerop
Copy link
Member

jerop commented Feb 9, 2022

/assign @jerop
/assign @pritidesai

@pritidesai
Copy link
Member

API WG - ready to merge
/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Feb 14, 2022
@tekton-robot tekton-robot merged commit 9c3ea19 into tektoncd:main Feb 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/tep Categorizes issue or PR as related to a TEP (or needs a TEP). lgtm Indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
Status: UnAssigned
Development

Successfully merging this pull request may close these issues.

4 participants