Name Request Release Report 22.5, v5.5.7

EPortman commented 3 weeks ago

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:
- Name Request UI v5.5.5 : 20291 move app to app directory
- Name Request UI v5.5.6 : 22425 update jurisdictions
- Name Request UI v5.5.7 : 22696 street address max 50 chars
[x] Ensure deployment steps are filled in - remove/replace placeholders
[x] Create a draft release in GitHub and confirm the correct commits are present
1. - [x] Confirm the correct commits are present
2. - [x] Select appropriate target is selected which represents the build in Test - either a commit from recent commits or a reference to a branch
3. - [x] Autogenerate release notes using last release tag as a point of reference. Update change list manually if required.
[x] Dev to ensure that the commit list is represented on the release report
[x] QA to schedule the release with staff/clients (daytime's best or when staff are available for rollback)
[x] All dev/test pipeline test suites green
[x] Dev/QA chat to plan prod verification testing (unless already automated)
[x] Post message that projects are being deployed to Prod in #registries-entities
[x] Release the code to production and complete smoke test
[x] Post message that projects have been deployed to Prod in #registries-entities and #entities-ops
[x] Finalise/publish the release in GitHub, tagging it

EPortman commented 3 weeks ago

Github Release Report https://github.com/bcgov/namerequest/releases Zenhub Release Report https://app.zenhub.com/workspaces/names-team-board-new-655554cbddd49510027dad2e/reports/release?release=Z2lkOi8vcmFwdG9yL1JlbGVhc2UvMTA0MDU0

EPortman commented 2 weeks ago

@ozamani9gh all tickets are in test and have been QA'd. This is ready for release.

Perhaps tomorrow morning?

bcgov / entity