website: Remove outdated distributions#4429
Conversation
Signed-off-by: Julius von Kohout <[email protected]>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
For ProKube @geier in autumn with the next release Prokube is also too far behind. |
|
@juliusvonkohout as far as I understood the full range of 26.03 (n) - 1.11(n-1) - 1.10 (n-2) is still fine to be listed on the website since it's about two major versions (patch releases are not listed on https://www.kubeflow.org/docs/kubeflow-distribution/releases/) as defined by the linked policy. (I don't have any involvement in the distributions listed there; just for transparency) cc @andreyvelich @chasecadet @thesuperzapper @franciscojavierarceo who know more around the intent of the new policy: I added kubeflow/community#1015 to clarify the wording |
Description of Changes
The KSC has voted and approved kubeflow/community#1002
so
For AKS @ritazh @mosabami @asw101 as in #4153
For Nutanix @johnugeorge #4122
For QBO @alexeadem #4111
please update your distributions.
We had 1.10.0 -> 1.10.1 -> 1.10.2 -> 1.11.0 -> 26.03.0 -> 26.03.1 https://github.com/kubeflow/community-distribution/releases, so some of your distribution are missing out for 5 releases.
"If a distribution no longer qualifies to be listed as a Kubeflow Distribution, its owners will
be notified of the reasons why via their contact details and will have 90 days to implement the
necessary changes.
If the distribution owners do not implement the changes or do not respond to requests, then the
distribution will be removed and will no longer be listed in the Kubeflow website."
You qualify hereby as notified.
cc @kubeflow/kubeflow-distribution-committee and @kubeflow/kubeflow-steering-committee
Related Issues
#4406