Skip to content
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

CHANGELOG: Deprecate customVersion = v1beta1 #257

Merged

Conversation

asymmetric
Copy link
Contributor

@asymmetric asymmetric commented Apr 25, 2018

We follow the release schedule of Kubernetes, according to which
deprecated versions are dropped after 3 releases.

v1beta2 was introduced in 1.8, thereby deprecating v1beta1, which
should therefore be dropped by 1.11.

customVersion = v1beta1 maps to a controller that uses apps/v1beta1,
which won't be updated, and that must therefore be droppped.

Signed-off-by: Lorenzo Manacorda lorenzo@kinvolk.io

@asymmetric asymmetric force-pushed the asymmetric/deprecations-0.6 branch 2 times, most recently from bc29f3b to e42f1fb Compare April 25, 2018 11:51
Copy link
Contributor

@krnowak krnowak left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure about doing a retroactive deprecation, but we need to update some announcements too. It probably doesn't matter much.

Maybe we should always mark previous custom versions as automatically deprecated whenever a new one is released?

CHANGELOG.md Outdated

* `Habitat` Manifests that do not specify a `customVersion`, or that specify a
`customVersion = v1beta1` are deprecated, and support for them will be removed
when Kubernetes 1.11 is released. Please upgrade your manifests by setting
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure I like the last sentence. Setting customVersion = v1beta2 is not enough. You need to use specv1beta2 field too. Maybe just drop this sentence or say something like "Please upgrade your manifests to the latest customVersion"?

@asymmetric
Copy link
Contributor Author

I think it's good to mark it as deprecated now, even if we should've done it before.

Maybe we should always mark previous custom versions as automatically deprecated

How would you do that? Were you thinking of adding that to the README?

@krnowak
Copy link
Contributor

krnowak commented May 2, 2018

How would you do that? Were you thinking of adding that to the README?

Yep. Just a kind of a statement or a policy.

Lorenzo Manacorda added 3 commits May 2, 2018 12:54
We follow the release schedule of Kubernetes, according to which
deprecated versions are dropped after 3 releases.

`apps/v1beta2` was [introduced][v1beta2] in 1.8, thereby deprecating `v1beta1`, which
should therefore be dropped by 1.11.

`customVersion = v1beta1` maps to a controller that uses `apps/v1beta1`,
which won't be updated, and that must therefore be droppped.

[v1beta2]: https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG-1.8.md#workloads-api-appsv1beta2

Signed-off-by: Lorenzo Manacorda <lorenzo@kinvolk.io>
To `release-process.md`.

Signed-off-by: Lorenzo Manacorda <lorenzo@kinvolk.io>
Signed-off-by: Lorenzo Manacorda <lorenzo@kinvolk.io>
@asymmetric asymmetric force-pushed the asymmetric/deprecations-0.6 branch from 88a8697 to 96070b0 Compare May 2, 2018 10:58
@asymmetric
Copy link
Contributor Author

Added it to the design doc.

@krnowak
Copy link
Contributor

krnowak commented May 2, 2018

LFAD. Could you add the deprecation notice here too? https://github.com/habitat-sh/habitat-operator/releases/tag/v0.6.0

@asymmetric asymmetric merged commit 65fdbb8 into habitat-sh:master May 2, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants