[cluster-api] Proposal for v1.0 release

[Vince Prignano]

Hi folks,

For the past few months, the Cluster API community has discussed the roadmap to v1beta1 and v1.0. The path thus far has been:

• v1alpha1 was the start of everything: try this out and see if things work out.

• v1alpha2 was the foundational release, we've re-architected most of our APIs and controllers to function around contracts and object references. We made composition a primary concept and started building on top of it.

• v1alpha3 is currently in maintenance mode. This release was driven by new features like health checks and control plane lifecycle management.

• v1alpha4 is the current stable version and is focused primarily on stability and iterative improvements.

• New features are going to be included in v0.4.x in the future behind feature gates, like the ClusterClass work described in this proposal.

Despite our API remaining in alpha state, the project is effectively operating with beta or higher guarantees. Most of our APIs have been supported for 1 year or longer, as in the case of v1alpha3. We have conversion webhooks between our types starting from v1alpha2, an extensive test matrix expanding with each new release as well as user and developer documentation.

After the September 8th community meeting, we’d like to propose the following:

• Code and API freeze starting on October 1st, 2021

• Bug fixes, improvements to the existing codebase, and existing feature gates functionalities are excluded from the freeze.

• To v1.0

• Create the v1.0 Milestone.

• Identify release-blocking issues and prioritize accordingly.

• Create a release-0.4 branch to support v0.4 / v1alpha4.

• Convert our current types to v1beta1 and provide conversion support from v1alpha3 and v1alpha4.

• Cut the final release.

• Update our Cluster API Enhancement Proposal (CAEP) template and contributing guide to add a section around breaking API or behavior changes.

• Plan a roadmap and backlog grooming sessions for future minor releases, based on 1.x.

• Amend the roadmap document with proposal freeze dates for each minor release.

• Continue working on security improvements, ClusterClass, Runtime Extensions, MachinePool Machines, and all other proposals in 1.x releases.

• Any proposals including breaking API changes are delayed until the community is ready to start v1beta2, or later.

As always, please feel free to reach out with any questions, comments, or concerns.

The Cluster API Maintainers.

[Carlos Tadeu Panato Jr]

this is great!

--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-cluster-lifecycle" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-cluster...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-cluster-lifecycle/BYAPR05MB43893148021758E11DF2E8E2B3D59%40BYAPR05MB4389.namprd05.prod.outlook.com.

[Fabrizio Pandini]

+1 from me

As a project we are already acting at this level

[dav...@gmail.com]

+1 to this plan! thanks folks.

[cecile...@gmail.com]

+ 1 from me as well

[Kris Nóva]

+1 

🎉

 congrats everyone - this is great! well deserved. 

--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-cluster-lifecycle" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-cluster...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-cluster-lifecycle/7bb784a6-f43d-4de7-b5f5-25f2d857cbf6n%40googlegroups.com.

[da...@devigned.com]

+1 -- The plan looks solid. Onto beta. Let's go!

[sbuer...@gmail.com]

+1

[Yuvaraj Kakaraparthi]

+1

[Michael McCune]

+1

[ta...@appscode.com]

+1

On Thursday, September 9, 2021 at 12:38:10 PM UTC-7 prig...@vmware.com wrote:

[Alberto Garcia Lamela]

+1

--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-cluster-lifecycle" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-cluster...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-cluster-lifecycle/9f1013df-8f30-481e-ab70-69fe57a8d936n%40googlegroups.com.

[Ankita Swamy]

+1

To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-cluster-lifecycle/CA%2B1G6Pm%3DER4nipZyLPNkX_VV2aXcW9nfZC7ZFpC4TYgMxyGz%3DA%40mail.gmail.com.