Release Calendar for 2026 : CRM Release Management Calendar - 2026

Scope of the Minor releases

• All New Projects
• Any Business Requirement or Enhancement, which required intensive testing.

User Story Completeness (Change Management Requirements)

• Every User Story must have an associated Change Request (CR) created in Helix.
• Each JIRA Story must include a clear description, solution/design details, and the impacted components.
• The Story Fix Version must reflect the target Major Release.
  • fixversion according to the major release fixVersion process : "major/{name of release} - {release number} - ({month name})" (e.g.: major/Dragonfly - R103 - (Dec))
• All related MR/PR links (merge request / pull request) must be included in the Story.
• Ensure the correct component is selected (CORE or iCARe).
• Ensure the status is set to “Ready for UAT” or “Ready for Production”, as applicable.

Major Release fixVersion process

When creating a Story as part of a Major Release for PROD deployment:

1. If you already know the intended PROD deployment date (based on expected development timelines), select the Fix Version using the format "major/{name of release} - {release number} - ({month name})" (e.g.: major/Dragonfly - R103 - (Dec)) and assign it to the Story.

Major Release Development to PROD Deployment Process:

• Developments need to be done on MajorDev1 & MajorDev2 (both Orgs: iCARe & CORE) sandbox
• Then it needs to be sent to MajorINT by developer (both Orgs: iCARe & CORE) and Update the Jira story status as "Ready for INT".
• From MajorINT, RM team will push the changes to INT (both Orgs: iCARe & CORE ).
• Then POs/ Developers will validate stories the INT. After successful INT Testing, Jira Status will be marked as 'Ready For UAT'
• RM team will Validate the UAT and on UAT deployment Date, RM team will Deploy to UAT and Story Status will be updated as "In UAT".
• Business User will 

Calendar of activities

The purpose of the Minor Release process is to provide clear visibility and predictable planning for deployments to UAT and Production, ensuring all changes follow defined timelines and approvals.

Key points

• Minor release deployments to PROD are planned for Monday, Tuesday, Wednesday, and Thursday, and must follow these rules:
  • All changes must be deployed to and tested in UAT first, in line with the deployment calendar.
  • Example: if a Story is planned for Tuesday PROD deployment, it must be tested in UAT before Monday 12:00 PM.
    • After 12:00 PM on Monday (i.e., one day before the planned deployment date / Fix Version), the RM (Change Coordinator) will consolidate the related Helix CRs and send them to the Change Manager for approval.
    • A developer must be available to support the Release Manager during UAT validation, if fixes are required.
    • After PROD deployment, the PO or developer can perform validation in PROD.
• There are no Friday PROD deployments, due to other RM related activities. If there is an urgent need, contact the Release Managers via the "Email" with proper explanation about urgency.  
• If the CR related to Jira story is not approved at least 1 day before the planned deployment date, the Story will not be deployed to PROD.