diff --git a/content/master/learn/feature-lifecycle.md b/content/master/learn/feature-lifecycle.md index 2da306daf..d04bbdb3c 100644 --- a/content/master/learn/feature-lifecycle.md +++ b/content/master/learn/feature-lifecycle.md @@ -22,11 +22,11 @@ Alpha features are off by default, and you must enable them by a feature flag, f removal or breaking changes without notice**, and aren't considered ready for use in production. -Sometimes alpha features require Crossplane to add fields to existing beta or GA +Sometimes alpha features require Crossplane to add fields to existing beta or GA API types. In these cases you must mark fields (for instance in their OpenAPI - schema) as alpha and subject to alpha API constraints (or lack thereof). + All alpha features should have an issue tracking their graduation to beta. @@ -43,11 +43,11 @@ instructions for migrating to the next version. This may require deleting, editing, and recreating API objects. The editing process may require some thought. This may require downtime for applications that rely on the feature. -Sometimes beta features require Crossplane to add fields to existing GA API types. In +Sometimes beta features require Crossplane to add fields to existing GA API types. In these cases you must mark fields (for instance in their OpenAPI schema) as beta - and subject to beta API constraints (or lack thereof). + All beta features should have an issue tracking their graduation to GA. diff --git a/content/v1.19/learn/feature-lifecycle.md b/content/v1.19/learn/feature-lifecycle.md index a52f0a536..ff70384d4 100644 --- a/content/v1.19/learn/feature-lifecycle.md +++ b/content/v1.19/learn/feature-lifecycle.md @@ -21,11 +21,11 @@ Alpha are off by default, and must be enabled by a feature flag, for example removal or breaking changes without notice**, and generally not considered ready for use in production. -In some cases alpha features require fields be added to existing beta or GA +In some cases alpha features require fields be added to existing beta or GA API types. In these cases fields must clearly be marked (for instance in their OpenAPI - schema) as alpha and subject to alpha API constraints (or lack thereof). + All alpha features should have an issue tracking their graduation to beta. @@ -42,11 +42,11 @@ instructions for migrating to the next version. This may require deleting, editing, and recreating API objects. The editing process may require some thought. This may require downtime for applications that rely on the feature. -In some cases beta features require fields be added to existing GA API types. In +In some cases beta features require fields be added to existing GA API types. In these cases fields must clearly be marked (for instance in their OpenAPI schema) as beta - and subject to beta API constraints (or lack thereof). + All beta features should have an issue tracking their graduation to GA. diff --git a/content/v1.20/learn/feature-lifecycle.md b/content/v1.20/learn/feature-lifecycle.md index a52f0a536..ff70384d4 100644 --- a/content/v1.20/learn/feature-lifecycle.md +++ b/content/v1.20/learn/feature-lifecycle.md @@ -21,11 +21,11 @@ Alpha are off by default, and must be enabled by a feature flag, for example removal or breaking changes without notice**, and generally not considered ready for use in production. -In some cases alpha features require fields be added to existing beta or GA +In some cases alpha features require fields be added to existing beta or GA API types. In these cases fields must clearly be marked (for instance in their OpenAPI - schema) as alpha and subject to alpha API constraints (or lack thereof). + All alpha features should have an issue tracking their graduation to beta. @@ -42,11 +42,11 @@ instructions for migrating to the next version. This may require deleting, editing, and recreating API objects. The editing process may require some thought. This may require downtime for applications that rely on the feature. -In some cases beta features require fields be added to existing GA API types. In +In some cases beta features require fields be added to existing GA API types. In these cases fields must clearly be marked (for instance in their OpenAPI schema) as beta - and subject to beta API constraints (or lack thereof). + All beta features should have an issue tracking their graduation to GA. diff --git a/content/v2.0-preview/learn/feature-lifecycle.md b/content/v2.0-preview/learn/feature-lifecycle.md index a52f0a536..ff70384d4 100644 --- a/content/v2.0-preview/learn/feature-lifecycle.md +++ b/content/v2.0-preview/learn/feature-lifecycle.md @@ -21,11 +21,11 @@ Alpha are off by default, and must be enabled by a feature flag, for example removal or breaking changes without notice**, and generally not considered ready for use in production. -In some cases alpha features require fields be added to existing beta or GA +In some cases alpha features require fields be added to existing beta or GA API types. In these cases fields must clearly be marked (for instance in their OpenAPI - schema) as alpha and subject to alpha API constraints (or lack thereof). + All alpha features should have an issue tracking their graduation to beta. @@ -42,11 +42,11 @@ instructions for migrating to the next version. This may require deleting, editing, and recreating API objects. The editing process may require some thought. This may require downtime for applications that rely on the feature. -In some cases beta features require fields be added to existing GA API types. In +In some cases beta features require fields be added to existing GA API types. In these cases fields must clearly be marked (for instance in their OpenAPI schema) as beta - and subject to beta API constraints (or lack thereof). + All beta features should have an issue tracking their graduation to GA. diff --git a/content/v2.0/learn/feature-lifecycle.md b/content/v2.0/learn/feature-lifecycle.md index 2da306daf..d04bbdb3c 100644 --- a/content/v2.0/learn/feature-lifecycle.md +++ b/content/v2.0/learn/feature-lifecycle.md @@ -22,11 +22,11 @@ Alpha features are off by default, and you must enable them by a feature flag, f removal or breaking changes without notice**, and aren't considered ready for use in production. -Sometimes alpha features require Crossplane to add fields to existing beta or GA +Sometimes alpha features require Crossplane to add fields to existing beta or GA API types. In these cases you must mark fields (for instance in their OpenAPI - schema) as alpha and subject to alpha API constraints (or lack thereof). + All alpha features should have an issue tracking their graduation to beta. @@ -43,11 +43,11 @@ instructions for migrating to the next version. This may require deleting, editing, and recreating API objects. The editing process may require some thought. This may require downtime for applications that rely on the feature. -Sometimes beta features require Crossplane to add fields to existing GA API types. In +Sometimes beta features require Crossplane to add fields to existing GA API types. In these cases you must mark fields (for instance in their OpenAPI schema) as beta - and subject to beta API constraints (or lack thereof). + All beta features should have an issue tracking their graduation to GA.