2024-03-06 Relias Academy release

Release Owner / Product Owner to Notify Stakeholders via Microsoft Teams Relias Academy Release Channel regarding this upcoming release. (link)

Release Owner / Deployment owner to Notify Platform Engineering and Communities teams regarding the upcoming release, in slack channels. ReliasEcom (#sprint-releases), Relias Engineering (#next-deployment)

Merge release_bacon (sprint name) branch into develop branch

Build and deploy develop branch to Staging and do a round of regression testing

Merge develop branch into oracle_ATG_upgrade_11.1_to_11.3.2 release branch

Check that there’s sufficient disk space on utility machine to do build and deploy

Build oracle_ATG_upgrade_11.1_to_11.3.2 branch

Properties files changes

DB changes?

Deploy to all instances

config change for https://relias.atlassian.net/browse/PAP-8832

check DB changes

Restart the instances

Purge cache on Cloudflare (purged https://reliasacademy.com/crsdocroot/content/css/relias/min/relias.css)

check Avalara tax code in dyn/admin

After code deployment is complete, start regression testing. (@Lakshmi Kondragunta @Henry Fu)

Trigger the Ghost Inspector tests (failures due to UI changes. modified tests so they pass for now. need to check with team to see if these are expected changes)

Verify all the tickets in the fix version and mark them as done

Release Owner to Mark Jira Release as Released, Mark CHM ticket as Complete

Release Owner to Notify Stakeholders via Microsoft Teams Release Channel that release is complete

Notify Stakeholders in Slack ReliasEcom > sprint-releases channel that release is complete, Engineering Slack too (next-deployment channel)

Relias Communities Platform

Release Info:

Any style and JavaScript changes (update the relias.css file): CSS changes.

Pre-release steps:

Release steps Relias Academy: (To Update all sections below)

Post Release Procedure: