/
Release Process

Release Process

Overview

This page establishes the ideal release schedule for CBE releases


Table of Contents


Change Requests

For change requests submitted at least 30 days before the delivery date, a 2-week UAT testing cycle will be implemented, following these steps:

  1. Upon receiving a CR request from CBE in JIRA, Intellimedia will assess feasibility and provide feedback on the timeline.

  2. Intellimedia will establish cutoff dates for CR requirement confirmation and SOW signoff to align with the testing cycle and planned delivery date.

  3. CBE will confirm all business requirements at least four days before the SOW signoff date.

  4. Intellimedia will provide the SOW to CBE two days before the SOW signoff deadline.

  5. CBE will complete the signoff before the deadline.

  6. Intellimedia will deploy all CR-related code to the UAT environment two weeks before release and document the UAT deployment date in the release notes on Confluence.

  7. CBE will report any identified issues within five business days of the UAT cycle to ensure timely resolution and approval.


Non-critical Bugs

For non-critical bugs, we will follow a similar 2-week UAT cycle with following steps:

  1. Upon receiving a ticket in JIRA, Intellimedia will assess the resolution time and provide a delivery date that accommodates the 2-week testing cycle.

  2. Intellimedia will deploy the relevant code to the UAT environment two weeks before release and document the UAT deployment date in the release notes on Confluence.

  3. CBE will report all identified issues within five business days to allow sufficient time for fixes and approvals.


Critical Bugs and Expedited Resolutions

For critical bugs or those requiring expedited resolution, a modified process will be followed:

  1. For critical bugs, this process may not always be feasible, and UAT testing will be evaluated on a case-by-case basis.

  2. Intellimedia will determine the UAT testing duration based on effort estimates.

  3. A defined time window for UAT testing and resolution will be shared by Intellimedia before deployment.

  4. CBE will provide approval within the specified timeframe to ensure timely release.


Emergency Change Requests

For CRs submitted with less than 30 days’ notice, Intellimedia will determine the UAT testing duration based on effort estimates and the delivery date provided by CBE.

Related content

2025.03.15 Scheduled Release
2025.03.15 Scheduled Release
More like this
2025.02.03 February Bugfixes Release
2025.02.03 February Bugfixes Release
More like this
2024.05.04 CBELIVE Release Notes - Sprint 5 Release
2024.05.04 CBELIVE Release Notes - Sprint 5 Release
More like this
Service Level Agreement
Service Level Agreement
More like this
2024.08/09 Back to School Updates
2024.08/09 Back to School Updates
More like this