Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

Business AR Release Sprint 23.4 #445

Open
15 of 16 tasks
hanlunBCRegistries opened this issue Oct 29, 2024 · 1 comment
Open
15 of 16 tasks

Business AR Release Sprint 23.4 #445

hanlunBCRegistries opened this issue Oct 29, 2024 · 1 comment
Assignees
Labels
Business AR BAR Names Team Ticket for Names Team to tackle

Comments

@hanlunBCRegistries
Copy link
Collaborator

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:
    • BAR UI: v3.3.4
    • BAR API: v1.1.1
    • BAR Process Paid Filings Job: No Version
  • 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)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Business AR BAR Names Team Ticket for Names Team to tackle
Projects
None yet
Development

No branches or pull requests

1 participant