-
Story
-
Resolution: Unresolved
-
Normal
-
ACM 2.17.0
-
None
Value Statement
Ensure the issue title clearly reflects the value of this user story to the
intended persona. (Explain the "WHY")
- ACM currently uses the phrase "upgrade" to describe both the available OCP versions for hub/managed clusters and the action of "upgrading" clusters. OpenShift OCP itself however, has made an organized effort to consolidate their use of this language to "update"/"updates", and have added the language to their official glossary.
- Our product management leadership has expressed approval with aligning on "updates" (though followup action has not yet been prioritized). (See our Slack conversation)
Definition of Done for Engineering Story Owner (Checklist)
- Instances of "upgrade" copy as described in the attached readme is replaced with "update" across all ACM
- See readme here: https://drive.google.com/file/d/1NODwa8YCLc04jABc9sXnbNg1SwiGNfpU/view?usp=sharing
- See tracking spreadsheet here: https://docs.google.com/spreadsheets/d/1jiFUwTe5GufVE6FjuCV9KEYd0JU_b7aeSC5W3FwxOr0/edit?usp=drive_link
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 template that you can access from [The Playbook](
and ensure doc acceptance criteria is met.
- Call out this sentence as it's own action:
- [ ] Link the development issue to the doc issue.
Support Readiness
- [ ] The must-gather script has been updated.
- is depended on by
-
ACM-29962 Deliver alignment for use of "Update" (replaces the term "Upgrade") in ACM console.
-
- New
-