2023-1-17 Craft/Magento Release
Release Info:
Change Management ticket: https://relias.atlassian.net/browse/CHM-3301 Jira Release: Link!
Release Owner: @Ian Shields (Deactivated)
Testing Assignment spreadsheet (Check ALL 4 TABS to see if any are assigned to you.)
Prerequisites:
Last day of sprint:
Create integration → staging PR for repos to be released
Post links to the PRs in a highly visible channel to signal to team members that they’re ready for review
Once Staging PRs are approved, during staging verification:
All code merged to Staging branch at least 2 business days before release
Run deploy scripts as needed
Tickets with configurations are assigned to developers
CHM ticket is created by Release Owner
Confirm fix version is applied to all tickets to be released. Use
No Release Impact fix version for tickets with no code or user-facing changes.Update the status of all tickets in the release to “Ready For Stage Testing”
If the staging deploy of Craft or Magento took longer than usual, communicate this to the team and discuss scheduling the release call for everyone.
If deployment will take substantially more time than ~20 minutes, please consider starting the release call with Manager, PM, Release Owner, QA Team Lead. Once the deployments are complete, open the release call to the rest of the team for testing and debugging.
Day of:
Clean Stable build on Stage, not updated since testing period began
All tickets in “ready to release” status
CHM approval given by Default reviewer - usually Matt
Create PRs for deploy
PRs are approved and code is merged into production branch on our repository
Message in the #sprint-releases channel that the release is beginning
Pre-Deploy:
Recent Automated tests run and results verified
Configuration Items: N/A
Code Deploy:
git push cloud production:Production
git tag -a CHM-3301 -m "1/17/23 Magento-Cloud Release" | git push --tags
# cd to craft repo, checkout+pull production then:
git tag -a CHM-3301 -m "1/17/23 Craft Release" | git push --tags*Sample snippet only, code deploy owner to verify prior to release. Do NOT trust the release owner.
Post Deploy Release Procedure: