Release train checklist

Awaiting Train

Team Awaiting Train
APM APM Board Status
SPM SPM Board Status
A&I AI Board Status

Master Build Status

Solution Build Unit Test Coverage 🚉 Kaizen 🚉 Atsumeru-Redux 🚉 Sensei.Jumpstart - Regression 🚉 Sensei.Cloud - altus-prod
ControlsV1 Build Status Test Coverage Release Release Release Release
Kaizen Build Status Test Coverage N/A Release Release Release
Atsumeru Build Status Test Coverage N/A N/A Release Release
Kusanagi Build Status N/A N/A N/A Release Release
Atsumeru Master Data Build Status N/A N/A N/A Release Release
Demo Data Build Status 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 🔥 Smoke Tests TBD
🚦 Regression Tests 🚦 Regression Tests TBD

Artifact Ring Status

Solution 🚉 Release Candidate (iq-atsumeru) 🚂 Canary 🚂 First release 🚂 GA
ControlsV1 Release Sensei.D365.SenseiControlsV1 package in Coruscant@Local feed in Azure Artifacts Sensei.D365.SenseiControlsV1 package in Coruscant@Prerelease feed in Azure Artifacts Sensei.D365.SenseiControlsV1 package in Coruscant@Release feed in Azure Artifacts
Kaizen Release Sensei.D365.SenseiProject package in Coruscant@Local feed in Azure Artifacts Sensei.D365.SenseiProject package in Coruscant@Prerelease feed in Azure Artifacts Sensei.D365.SenseiProject package in Coruscant@Release feed in Azure Artifacts
Atsumeru Release Sensei.D365.SenseiProjectIndependent package in Coruscant@Local feed in Azure Artifacts Sensei.D365.SenseiProjectIndependent package in Coruscant@Prerelease feed in Azure Artifacts Sensei.D365.SenseiProjectIndependent package in Coruscant@Release feed in Azure Artifacts
Kusanagi Release Sensei.D365.SenseiAltusCopilot package in Coruscant@Local feed in Azure Artifacts Sensei.D365.SenseiAltusCopilot package in Coruscant@Prerelease feed in Azure Artifacts Sensei.D365.SenseiAltusCopilot package in Coruscant@Release feed in Azure Artifacts
Atsumeru Master Data Release Sensei.D365.SenseiProjectIndependent_MasterData package in Coruscant feed in Azure Artifacts Sensei.D365.SenseiProjectIndependent_MasterData package in Coruscant feed in Azure Artifacts Sensei.D365.SenseiProjectIndependent_MasterData package in Coruscant feed in Azure Artifacts
Demo Data N/A Sensei.D365.SenseiProjectIndependent_DemoData package in Coruscant feed in Azure Artifacts Sensei.D365.SenseiProjectIndependent_DemoData package in Coruscant@Prerelease feed in Azure Artifacts Sensei.D365.SenseiProjectIndependent_DemoData package in Coruscant@Release feed in Azure Artifacts
Oldest Supported Version N/A Canary FR GA

Release procedure

Fortnightly Procedure

Only IF today is NOT end of a sprint tomorrow THEN

Weekly Procedure

  1. Check UI test results:
  2. 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.
  3. Approve artifacts for release in sensei.cloud (Latest) to go to local (canary) artefact feed
    Only release branch builds.
  4. 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):
  5. Back to artifacts
    • Verify that any approved artifacts jobs succeeded
  6. 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 buggy version adjust the corresponding version JSON file.
These files are used by the Hub to populate the artifact version selection.

Altus for Teams Altus for Teams

Build Unit Test Coverage Latest 🚂 Canary 🏛️ GCCH Canary 🚂 1st Release 🚂 GA 🏛️ GCCH GA
Build Status Test Coverage Latest Canary GCCH Canary First release Production GCCH Production

Release procedure:

  1. Find correct run of pipeline and Run stage & approve it

Altus for Word Altus for Word

Build Unit Test Coverage Latest 🚂 Canary 🏛️ GCCH Canary 🚂 1st Release 🚂 GA 🏛️ GCCH GA
Build Status Test Coverage Latest Canary GCCH Canary First release GA GCCH GA

Release procedure:

  1. Approve release stage

Altus for Project

Prepare release (before release meeting):

  1. Create PR from develop to main
  2. Approve & finish Pull Request

Release procedure:

  1. Approve release stage of both pipelines

Altus for Project - MSI Altus for Project - MSI

Build Unit Test Coverage Latest 🚂 Canary 🚂 1st Release 🚂 GA
Build Status Test Coverage Canary Canary First release GA

Altus for Project - ClickOnce Altus for Project - Click Once

Build Unit Test Coverage Latest 🚂 Canary 🚂 1st Release 🚂 GA
Build Status Test Coverage Canary Canary First release GA

Altus Reporting Altus Reporting

  • Process Coming soon... (Nikhi)

Altus Hub

Environment Build Deploy
Altus Hub Development Build Status Build Status
Altus Hub Production Build Status Build Status

Prepare release (before release meeting):

  1. Create PR from dev to main
  2. Approve & finish Pull Request

Release procedure:

  1. Run stage 'Deploy' & approve it

Sensei Hub Releases

GCC-High Deployments

Use the GCC-High Deployment pipeline to deploy to customers in slow mode.

Canary:

  • none

First Release:

  • none

General Availability:

Release anomalies - Last 10 or relevant

2026-10-08 - Direct from master to Canary

Delayed creation of RC due to illness and merge issues to release branch. Deploy master direct to Canary as current Canary has a too high number of fixed defects.

  • ControlsV1 - 2026.10.08.1
  • SenseiProjectIndependent - 2026.10.08.1
  • SenseiAltusCopilot - 2026.09.29.3

2026-09-24 - Delayed RC

Delayed creation of RC. Waited to confirm the fix below is working, so a corrected RC can be created more easily if needed.

2026-09-22 - Direct from RC to GA

Due to #47644 push release to Canary, FR and GA.

Pushed the following versions

  • ControlsV1 - 2026.08.18.19
  • SenseiProjectIndependent - 2026.09.22.4