Names 19.5 - NAMEX API Pre Release Checklist

[Rajandeep98]

Prior to moving into production, the following steps should be completed or confirmed:

• Add release # to this ticket

• Update version numbers in the code being released and list them here:

  • Namex API v1.1.44

• Ensure deployment steps are filled in - remove/replace placeholders

• Create a draft release in GitHub and confirm the correct commits are present

1. • Confirm the correct commits are present
2. • Select appropriate target is selected which represents the build in Test - either a commit from recent commits or a reference to a branch
3. • 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
• 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:

• Namex API - v1.1.44 done by CD script

Test:

• Namex API - v1.1.44 done by XX on Nov X

Prod:

• Namex API - v1.1.44 done by XX on Nov X
• Notify the team via the #registries-ops channel

Smoke Test Script

• load Filings UI
• load Edit UI, eg, start change or alteration filing
• load Create UI, eg, start an IA or registration or voluntary dissolution
• watch Sentry logs for 60 minutes
• watch Kibana logs for 60 minutes