-
Notifications
You must be signed in to change notification settings - Fork 3.3k
Snapshot the Kubernetes 1.16 release #1141
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
Snapshot the Kubernetes 1.16 release #1141
Conversation
palnabarun
commented
Apr 9, 2020
- Update version constants
- Generate client
- Apply hotfixes
- KUBERNETES_BRANCH to "release-1.16" - CLIENT_VERSION to "12.0.0-snapshot" - DEVELOPMENT_STATUS to "3 - Alpha"
Edit: Oops! Never mind. Saw your comment on the other PR. 😅 |
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 @palnabarun. Would you mind collecting the API changes in CHANGELOG, or is @scottilee going to collect them in the 12.0.0a1 release PR?
|
||
# Name of the release package | ||
PACKAGE_NAME = "kubernetes" | ||
|
||
# Stage of development, mainly used in setup.py's classifiers. | ||
DEVELOPMENT_STATUS = "4 - Beta" | ||
DEVELOPMENT_STATUS = "3 - Alpha" |
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.
nit: we have been using Beta in the master branch (x.0.0-snapshot) meaning a "dev" status. It doesn't have any real effect since we don't publish the snapshot client. Perhaps Alpha fits it better. I think we can stick with one and don't need to toggle between Alpha and Beta in the future
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.
I was researching what should be the classifier for an upstream development branch, but couldn't find any concrete precedence for our use case.
I thought settling for Alpha would make more sense than Beta.
I think we can stick with one and don't need to toggle between Alpha and Beta in the future
👍
I was thinking that collecting them in the 12.0.0a1 PR would make more sense as one single commit can have all kinds of changes in the CHANGELOG and cherry-pick would thus become easier. |
/assign |
@roycaihw I have updated this PR with the API changes collected from upstream. Added them under a heading |
The changes are collected from upstream [CHANGELOG](https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.16.md)
41dbde2
to
afd837a
Compare
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.
nit: I noticed that kubernetes-client/gen#155 was not included. It could be included in this PR or in a separate one
/lgtm
/approve
|
||
Kubernetes API Version: 1.16.9 | ||
|
||
**API Change:** |
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.
Awesome. Thanks for collecting the API changes!
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: palnabarun, roycaihw 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 |
I cut this PR before that change went in. The next PR incorporating update of OpenAPI generator would have the kubernetes-client/gen#155 as well as kubernetes-client/gen#154 |
Thanks for the approval. 🙂 |