Release Cycle

Starting with the v1.10.0 release, Crossplane is released on a quarterly (13 week) cadence. A cycle is comprised of three general stages:

Weeks 1—11: Active Development
Week 12: Feature Freeze
Week 13: Code Freeze

This results in four releases per year, with the most recent three releases being maintained at any given time. When a new release is cut, the fourth most recent release reaches end of life (EOL). Users can expect any given release to be maintained for nine months.

Feature Lifecycle

Crossplane follows a similar feature lifecycle to upstream Kubernetes. All major new features must be added in alpha. Alpha features are expected to eventually graduate to beta, and then to general availability (GA). Features that languish at alpha or beta may be subject to deprecation.

Alpha Features

Alpha are off by default, and must be enabled by a feature flag, for example --enable-composition-revisions. API types pertaining to alpha features use a vNalphaN style API version, like v1alpha. Alpha features are subject to removal or breaking changes without notice, and generally not considered ready for use in production.

Learn More on Crossplane

Release Cycle

Feature Lifecycle

Feature Lifecycle

Alpha Features