-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Deprecation Notice for Results Field for PipelineRuns and TaskRuns #1278
Conversation
Hi @danielhelfand. Thanks for your PR. I'm waiting for a tektoncd member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/ok-to-test
@@ -112,7 +115,9 @@ type PipelineRef struct { | |||
type PipelineRunStatus struct { | |||
duckv1beta1.Status `json:",inline"` | |||
|
|||
// In #107 should be updated to hold the location logs have been uploaded to | |||
// Deprecation Notice: The field Results will be deprecated in v0.8.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
will be deprecated in v0.8.0
-> will be removed in v0.8.0
. I think we're technically deprecating it in 0.7.0 by making the announcement :)
Same comment for the other lines/files where this notice appears.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for catching that. Changed to will be removed in v0.8.0.
/lgtm |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks @danielhelfand 😃
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: danielhelfand, dibyom 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 |
@dibyom Happy to help! Appreciate your review. |
Thanks @danielhelfand !! ❤️ |
@bobcatfish Sure thing! Thanks for writing up the issue. |
As discussed in #1268, there should be proper notice given before addressing #1243. The plan is to announce in release notes for 0.7.0 that the
Results
field for pipelineruns and taskruns will be removed by v0.8.0.This pull request adds code comments to the API to create awareness about
Results
going away in 0.8.0. I also addressed some typos inapi_compatibility_policy.md
.Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:
Reviewer Notes
If API changes
are included, additive changes
must be approved by at least two OWNERS
and backwards incompatible changes
must be approved by more than 50% of the OWNERS,
and they must first be added
in a backwards compatible way.
Release Notes