Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

SRE 19.4 - NAMEREQUEST UI Pre Release Checklist #18478

Closed
16 of 24 tasks
eve-git opened this issue Nov 6, 2023 · 0 comments
Closed
16 of 24 tasks

SRE 19.4 - NAMEREQUEST UI Pre Release Checklist #18478

eve-git opened this issue Nov 6, 2023 · 0 comments
Assignees
Labels
Name Request Names Team Name Request Name Examination Team

Comments

@eve-git
Copy link
Collaborator

eve-git commented Nov 6, 2023

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:
    • Name Request UI v5.3.8
  • Ensure deployment steps are filled in - remove/replace placeholders
  • Create a draft release in GitHub and confirm the correct commits are present
    • 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
  • 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:

Name Request UI - v5.3.8 done by CD script

Test:

Name Request UI - v5.3.8 done by CD script

Prod:

  • Name Request UI - v5.3.8 done by CD script
  • Notify the following TEAMS GROUPS ops, entities and Names channels

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
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
Name Request Names Team Name Request Name Examination Team
Projects
None yet
Development

No branches or pull requests

5 participants