-
Feature
-
Resolution: Duplicate
-
Minor
-
None
-
None
-
None
-
XS
-
False
-
-
False
-
0% To Do, 0% In Progress, 100% Done
-
-
Feature Overview (aka. Goal Summary)
Backstage Operator is still being improved, new features are being added, and changes to the Backstage CR API are inevitable. Some changes are critical and require clear policy and communication so that the user can be prepared.
To reduce the maintenance overhead, we'll be deprecating the v1alpha3 CRD version, and consider removing it in $currentFixVersion+2 releases. Like if announced as deprecated in 1.9.0, we'll consider removing it in 1.11.0 (or a 2.y).
Goals (aka. expected user outcomes)
- reduce the maintenance overhead
Requirements (aka. Acceptance Criteria):
- Backstage v1alpha3 API deprecation in both upstream and downstream documentation
Out of Scope (Optional)
- Automated upgrade
- Merging tools
Documentation Considerations
- Make sure each API deprecation case is properly documented in RN.
- depends on
-
RHIDP-4312 [Operator] Deprecate CRD v1alpha1 and v1alpha2 versions
-
- Closed
-
- duplicates
-
RHDHPLAN-317 [Operator] Deprecate CRD v1alpha3 version
-
- In Progress
-
- is related to
-
RHIDP-4370 Introduce v1alpha3 of Backstage CRD
-
- Closed
-
-
RHIDP-4312 [Operator] Deprecate CRD v1alpha1 and v1alpha2 versions
-
- Closed
-