Document Deprecation Requirements for CLI

[danielhelfand]

There is no documentation currently on the approach that should be used to deprecate or change features of the CLI that will break backwards compatibility. At the moment, there is an informal approach used, which is to give a full release to warn about a breaking change, log a message from the CLI when applicable to give users a more direct warning about the change, and document that deprecation notice or behavior change in release notes for the version before when the change will take place.

Pipeline has a policy for API changes that we can use as a reference. This issue can serve as a place of discussion for if there are CLI-specific issues that should be considered for this, and this approach can be introduced at any time once there is an agreement in place. At the very least, the approach should be presented and agreed upon in a CLI working group.

[tekton-robot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
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.

/lifecycle stale

Send feedback to tektoncd/plumbing.

[tekton-robot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.

/lifecycle rotten

Send feedback to tektoncd/plumbing.

[tekton-robot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Send feedback to tektoncd/plumbing.

[tekton-robot]

@tekton-robot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Send feedback to tektoncd/plumbing.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.