-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Things to do before the v1 version is released #7398
Comments
@tao12345666333: This issue is currently awaiting triage. If Ingress contributors determines this is a relevant issue, they will accept it by applying the The 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. |
I don't know if we can create a pre-release helm chart the same way we do with releases here in Github. One like "this is the latest but you need to install it manually" Is that possible? |
https://artifacthub.io/docs/topics/annotations/helm/ Maybe we can cut a helm 4.0 pointing to controller v1.0, kubeVersion >=1.19, and the annotation of pre-release @strongjz thoughts? |
As far as I know, it should not work. Once released, even if it is a pre-release status in GitHub, our helm repo will not distinguish it. But I'm happy to try it. |
@rikatz After a quick verification, it can be realized, as long as the version number conforms to this specification. https://semver.org/#spec-item-9
|
@kd7lxl see the description as well, added the required cherry picks before merging |
In order to facilitate our v1 release, we need to list some planned things for follow-up.
Existing issues:
changes
docs
release
Code Freeze and Release
After the above issues are solved and the changes merged a code freeze will be in place
cc @rikatz @strongjz
Please add or modify this content directly.
If others need to review a PR or issue that needs to be reviewed before the v1 version is released, please also add
/remove-kind bug
The text was updated successfully, but these errors were encountered: