diff options
| author | Jordan Liggitt <liggitt@google.com> | 2019-04-24 09:53:31 -0400 |
|---|---|---|
| committer | Jordan Liggitt <liggitt@google.com> | 2019-04-24 09:53:31 -0400 |
| commit | 4add2dbfd254b05abf170afc3f4839dd4546b8e2 (patch) | |
| tree | 48604910b8784a8aec919fa34d5b03a3fb383309 | |
| parent | bd859aca8a4001b76da02b5cb57672103c39979a (diff) | |
Add field/validation/behavior change to API review requirements
| -rw-r--r-- | sig-architecture/api-review-process.md | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/sig-architecture/api-review-process.md b/sig-architecture/api-review-process.md index 4c3542b6..181607e9 100644 --- a/sig-architecture/api-review-process.md +++ b/sig-architecture/api-review-process.md @@ -69,6 +69,7 @@ Ideally, those whose API review priority is shifted in a release-impacting way w * Any new resource type * Any new version of a stable API * Any new functionality added to a stable API as defined by SIG Architecture and the API Reviewers + * Any change to the meaning, validation, or behavior of a field * The existing [API conventions](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md) (and [API change guidelines](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api_changes.md), if applicable) have been read and followed. 1. Request an API review for a PR or issue in the kubernetes org by adding the `api-review` label with a `/label api-review` comment (requests can be cancelled with a `/remove-label api-review` comment) |