Skip to content

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.

Sign up for GitHub

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

Merged
merged 4 commits into from
May 11, 2020
Merged

Snapshot the Kubernetes 1.16 release #1141

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
3f0e7c7
Update constants
palnabarun Mar 30, 2020
c206745
Generate updated client
palnabarun Apr 2, 2020
739665e
Apply hotfixes
palnabarun Apr 2, 2020
afd837a
Add 1.16 API changes to CHANGELOG
palnabarun Apr 28, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions scripts/constants.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,16 +15,16 @@
import sys

# Kubernetes branch to get the OpenAPI spec from.
KUBERNETES_BRANCH = "release-1.15"
KUBERNETES_BRANCH = "release-1.16"

# client version for packaging and releasing.
CLIENT_VERSION = "11.0.0-snapshot"
CLIENT_VERSION = "12.0.0-snapshot"

# 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"
Copy link
Member

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

Copy link
Member Author

@palnabarun palnabarun Apr 10, 2020 •
edited
Loading

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

👍



# If called directly, return the constant value given
Expand Down