-
Story
-
Resolution: Unresolved
-
Undefined
-
ACM 2.10.0
-
False
-
None
-
False
-
-
No
-
-
Value Statement
It can be difficult to keep VolSync support for older versions up to date when it comes to CVEs and dependencies. Previously we've tried to align support for VolSync with specific ACM versions, which means long support lifecycles (and lifecycles are getting longer now with OCP extending their support windows).
Technically there is no tie to force VolSync to stay at an older version with older ACM versions. This will allow VolSync to be decoupled more and also lower the costs of maintaining VolSync.
Generally VolSync users will want to be on current versions to get all latest features and dependency updates.
Current support lifecycle looks like this:
| Version | Tier | OpenShift Version | General availability | Full support ends | Maintenance ends | EUS ends |
|---|---|---|---|---|---|---|
| Previous operator releases without a tiered strategy | ||||||
| 0.8 | N/A | 4.12, 4.13, 4.14 | 15 Nov 2023 | 16 Dec 2024 | 17 Jun 2025 | N/A |
| 0.7 | 4.10, 4.11, 4.12, 4.13, 4.14 | 08 Jun 2023 | 09 Jul 2024 | 10 Dec 2024 | N/A | |
| 0.6 | 4.10, 4.11, 4.12, 4.13 | 06 Feb 2023 | 07 Mar 2024 | 09 Jul 2024 | N/A | |
| 0.5 | 4.9, 4.10, 4.11, 4.12 | 29 Aug 2022 | 11 Sep 2023 | 13 Dec 2023 | N/A |
Starting with the release of VolSync v0.9.0 we'd like to update it to be:
| Version | Tier | OpenShift Version | General availability | Full support ends | Maintenance ends | EUS ends |
|---|---|---|---|---|---|---|
| Previous operator releases without a tiered strategy | ||||||
| 0.9 | 4.12, 4.13, 4.14 | (when ACM 2.10 ships - Using March 2024 for this example) | Release of 0.11 | Release of 0.11 | N/A | |
| 0.8 | N/A | 4.12, 4.13, 4.14 | 15 Nov 2023 | Release of 0.10 | Release of 0.10 | N/A |
| 0.7 | 4.10, 4.11, 4.12, 4.13, 4.14 | 08 Jun 2023 | March 2024 | March 2024 | N/A | |
| 0.6 | 4.10, 4.11, 4.12, 4.13 | 06 Feb 2023 | March 2024 | March 2024 | N/A | |
| 0.5 | 4.9, 4.10, 4.11, 4.12 | 29 Aug 2022 | 11 Sep 2023 | 13 Dec 2023 | N/A |
Definition of Done for Engineering Story Owner (Checklist)
- VolSync v0.9.0 will need to be built to support OCP 4.10 & 4.11 (current downstream builds are only packaged for 4.12-4.15)
- Documentation updates - will need instructions for users on older ACM versions to update to newer VolSync versions
- discussed with Jake Berger and created documentation task: https://issues.redhat.com/browse/ACM-10015
Development Complete
- The code is complete.
- Functionality is working.
- Any required downstream Docker file changes are made.
Tests Automated
- [ ] Unit/function tests have been automated and incorporated into the
build. - [ ] 100% automated unit/function test coverage for new or changed APIs.
Secure Design
- [ ] Security has been assessed and incorporated into your threat model.
Multidisciplinary Teams Readiness
- [ ] Create an informative documentation issue using the [Customer
Portal_doc_issue template](
https://github.com/stolostron/backlog/issues/new?assignees=&labels=squad%3Adoc&template=doc_issue.md&title=),
and ensure doc acceptance criteria is met. Link the development issue to
the doc issue. - [ ] Provide input to the QE team, and ensure QE acceptance criteria
(established between story owner and QE focal) are met.
Support Readiness
- [ ] The must-gather script has been updated.
- is related to
-
-
- In Progress
-