-
Notifications
You must be signed in to change notification settings - Fork 1.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
📖 : Add beta testing tasks to release process #8552
📖 : Add beta testing tasks to release process #8552
Conversation
@@ -373,6 +374,14 @@ Stakeholders are: (TBD) | |||
* Provider implementers | |||
* ... | |||
|
|||
#### Communicate beta to providers | |||
|
|||
The goal of this task is to inform all providers that a new beta.0 version a release is out and that it should be tested. We want to prevent issues where providers don't have enough time to test before a new version of CAPI is released. This stems from a previous issue we are trying to avoid: https://github.com/kubernetes-sigs/cluster-api/issues/8498 |
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.
As we can't really inform all providers directly let's make a minimal list of the most active providers to inform - or perhaps all providers under kubernetes-sigs.
Below list from: https://github.com/orgs/kubernetes-sigs/repositories?language=&q=cluster-api&sort=&type=all
AWS: https://github.com/kubernetes-sigs/cluster-api-provider-aws
Azure: https://github.com/kubernetes-sigs/cluster-api-provider-azure
GCP: https://github.com/kubernetes-sigs/cluster-api-provider-gcp
Openstack: https://github.com/kubernetes-sigs/cluster-api-provider-openstack
IBMCloud: https://github.com/kubernetes-sigs/cluster-api-provider-ibmcloud
vSphere: https://github.com/kubernetes-sigs/cluster-api-provider-vsphere
Addon provider helm: https://github.com/kubernetes-sigs/cluster-api-addon-provider-helm
Packet: https://github.com/kubernetes-sigs/cluster-api-provider-packet
Operator: https://github.com/kubernetes-sigs/cluster-api-operator
Nested: https://github.com/kubernetes-sigs/cluster-api-provider-nested
Kubemark: https://github.com/kubernetes-sigs/cluster-api-provider-kubemark
Kubevirt: https://github.com/kubernetes-sigs/cluster-api-provider-kubevirt
Cloudstack: https://github.com/kubernetes-sigs/cluster-api-provider-cloudstack
Digital Ocean: https://github.com/kubernetes-sigs/cluster-api-provider-digitalocean
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 reordered but they should all be there.
2966210
to
caedee8
Compare
caedee8
to
e7eae9d
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.
/lgtm
I think this is a good process to start with and we can refine / automate as needed going forward.
LGTM label has been added. Git tree hash: 4c601f648cff68931b2096069d816fa2ffecfdd5
|
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sbueringer 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 |
What this PR does / why we need it:
As discussed in #8498 (comment) we want to inform providers when a new beta.0 has been released. This will help 1) inform the providers of the upcoming release and 2) let them know a new version is ready to test. The beta.0 release should give the providers about a month of testing before the next minor release.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Ref #8498