[ANNOUNCE] Maturity Levels for Kubeflow Subprojects – Feedback Wanted

[Andrey Velichkevich]

Hi everyone,

We’ve opened a proposal defining maturity levels for Kubeflow subprojects and would love your feedback before we merge it.

PR link: https://github.com/kubeflow/community/pull/965

  

As Kubeflow moves through CNCF graduation, we need a clear, consistent way to categorize subprojects so maintainers and users share the same expectations – especially around support and deprecation.

What's proposed – four (4) maturity levels:

•   Graduated – ready for general availability
•   Incubating – actively developed, not all pieces in place yet
•   Deprecated – development halted; no new versions planned. Released assets remain available for at least 2 minor releases or 1 year
•   Archived – closed projects (e.g. kfctl)
  

Please leave your feedback and suggestions directly on the PR. We'd like to gather feedback over this week – please review by June 15th.

If you are maintainer of Kubeflow subproject, your input is especially welcome.

Thanks,

Andrey