Release train checklist

Awaiting Train

Team	Awaiting Train
APM
SPM
A&I

Master Build Status

Solution	Unit Test Coverage	🚉 Kaizen	🚉 Atsumeru-Redux	🚉 Sensei.Jumpstart - Regression	🚉 Sensei.Cloud - altus-prod
ControlsV1
Kaizen		N/A
Atsumeru		N/A	N/A
Kusanagi	N/A	N/A	N/A
Atsumeru Master Data	N/A	N/A	N/A
Demo Data	N/A	N/A	N/A	N/A	N/A

UI Test

Test \ Environment	🚉 Sensei.Jumpstart - Regression (Master branch)	🚉 Release Candidate (iq-atsumeru) (Release branch)
🔥 Smoke Tests		TBD
🚦 Regression Tests		TBD

Artifact Ring Status

Solution	🚉 Release Candidate (iq-atsumeru)	🚂 Canary	🚂 First release	🚂 GA
ControlsV1
Kaizen
Atsumeru
Kusanagi
Atsumeru Master Data
Demo Data	N/A
Oldest Supported Version	N/A

Release procedure

Fortnightly Procedure

Only IF today is NOT end of a sprint tomorrow THEN

Promote pre-release artifacts (First Release) to release (GA)
- SenseiAltusCopilot
- SenseiControlsV1
- SenseiProject (Kaizen)
- SenseiProjectIndependent (Atsumeru)
- SenseiProjectIndependent (Atsumeru) DemoData
- SenseiProjectIndependent (Atsumeru) MasterData
Promote local artifacts (Canary) to pre-release (First Release)
- SenseiAltusCopilot
- SenseiControlsV1
- SenseiProject (Kaizen)
- SenseiProjectIndependent (Atsumeru)
- SenseiProjectIndependent (Atsumeru) DemoData
- SenseiProjectIndependent (Atsumeru) MasterData
Docs changes:
- Next GA Release - Remove Paginated reports from Solution Starters
- any other old stuff can be removed from Docs? - go through the release notes

Weekly Procedure

Check UI test results:
- - 🔥 Smoke Tests
- - 🚦 Regression Tests
Open ADO boards and check the following:
- Review tickets in [Awaiting Train] columns.
  - Check if [Description] has been provided.
  - Check if [Release Note] has been provided (for applicable tickets), and the possibility of adding visual (screenshot or animation) when applicable.
    - Release Notes will be copied into docs. Add NA or N/A to be omitted from release notes.
  - Check if [Release Category] has been provided. Check Category for options.
    - Release Category will be copied into docs.
  - Check if [Acceptance Criteria] is properly written.
  - Confirm successful test.
  - For Research and Development ticket, check if ticket fields have been filled and the summary of results is properly documented.
- Check if there are tickets in [Review] or [In Testing - Done] can/should be part of the train and apply the same checks.
- For each tickets that can be claimed, check if [Effort] is not empty, check if it needs to be updated.
- Move claimed tickets to [Done] column.
- If needed (this is now optional under Scrum), walk the board to identify if we have old tickets in WIP.
Approve artifacts for release in sensei.cloud (Latest) to go to local (canary) artefact feed
Only release branch builds.
Create & Approve & Finish Pull Request from master to release branch in GitHub (NOTE: Do not move past this step until 3 approvals are posted per PR):
- Kaizen.PCFControls
- Kaizen
Back to artifacts
- Verify that any approved artifacts jobs succeeded
Validate Pull Request from Step 4 have auto-merge enabled and have 3 approvals. The checks on the PR will run for ~20 minutes.

Warning

Make sure the artifact publish succeeds. Publishing one artifact and not others can lead to broken environments.

Note

In case of fix release or removal of bugged version adjust the corresponding version JSON file.
These files are used by the Hub to populate the artifact version selection.