entity
entity copied to clipboard
Names Sprint Release 21.1 - NAMEX API Pre Release Checklist
Prior to moving into production, the following steps should be completed or confirmed:
- [x] Add release # to this ticket
- [x] Update version numbers in the code being released and list them here:
- Namex API -v11.1.52
- Namex-pay -v0.1.5
- [ ] Ensure deployment steps are filled in - remove/replace placeholders
- [ ] Create a draft release in GitHub and confirm the correct commits are present
-
- [x] Confirm the correct commits are present
-
- [ ] Select appropriate target is selected which represents the build in Test - either a commit from recent commits or a reference to a branch
-
- [ ] Autogenerate release notes using last release tag as a point of reference. Update change list manually if required.
- [ ] Dev to ensure that the commit list is represented on the release report
- [ ] QA to schedule the release with staff/clients (daytime's best or when staff are available for rollback)
- [ ] All dev/test pipeline test suites green
- [ ] Dev/QA chat to plan prod verification testing (unless already automated)
- [ ] Post message that projects are being deployed to Prod in [#registries-entities]
- [ ] Post message that projects are being deployed to Prod in [#OCM Team]
- [ ] Post message that projects are being deployed to Prod in [#NAMES Team]
- [ ] (https://chat.developer.gov.bc.ca/channel/registries-entities)
- [ ] Release the code to production and complete smoke test (STEPS BELOW)
- [ ] Post message that projects have been deployed to Prod in #registries-entities and #entities-ops
- [ ] Finalise/publish the release in GitHub, tagging it
- [ ] Merge release branch back to master (if applicable)
- [ ] Change openshift builds/pipelines back to master (if applicable)
Deployment Steps
Dev:
- [x] Namex API -v11.1.52 By CD
- [x] Namex-pay -v0.1.5 By CD
Test:
- [x] Name request UI -v11.1.52 by CD
- [x] Namex-pay -v0.1.5 By CD
Prod:
- [ ] Name request UI -v11.1.52 by CD
- [ ] Namex-pay -v0.1.5 By CD