-
Notifications
You must be signed in to change notification settings - Fork 498
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
Conformance Profiles (GEP 1709) to Experimental status #2180
Conformance Profiles (GEP 1709) to Experimental status #2180
Conversation
Skipping CI for Draft Pull Request. |
Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it. 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.
Thanks @shaneutt!
/approve
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 @shaneutt!
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: arkodg, mlavacca, robscott, shaneutt, sunjayBhatia 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 |
d572ebc
to
243f087
Compare
243f087
to
7671e03
Compare
@@ -71,7 +71,8 @@ proposed changes in our API. In some cases, these changes will be documentation | |||
only, but in most cases, some API changes will also be required. It is important | |||
that every new feature of the API is marked as "Experimental" when it is | |||
introduced. Within the API, we use `<gateway:experimental>` tags to denote | |||
experimental fields. | |||
experimental fields. Within Golang packages (conformance tests, CLIs, e.t.c.) we |
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.
The original justification for the build flag was provisional status of the GEP. Is the flag still necessary now that it's experimental? @shaneutt
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.
Because it's a replacement for the normal CLI and test suite, the intention was to leave it, however I suppose we can have a discussion about removing the build tag if that's helpful to people. 🤔
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.
The build tag is a (soft) blocker for our adoption personally
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.
Would also be in favor of dropping experimental build tag here, ideally pre-0.8.0 so it's a bit easier to report results.
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.
Sounds good #2242
What type of PR is this?
/kind cleanup
/kind gep
What this PR does / why we need it:
In support of #1709 this moves the GEP to
Experimental
status, ready for implementations to start submitting their reports.