Process
The website upgrades phase will follow that same process as the past:
- [We] will Create D11 feature branch
- [You] will have 2 weeks to Identify and fix any issues, then once you let me know
- [We] Merge D11 website to become LIVE
The whole process will be communicated and tracked via a service desk ticket
Upgrade Schedule
Each group will 'close off' midday the Friday prior. ie to be included in Group E, you will need to complete the form by 12pm Friday 28 February.
| Group | Cut Off |
|---|---|
| Group H: 25 March - 8 April 2026 | 12PM 20 March 2026 |
| Group I: 1 April - 15 April 2026 | 12PM 27 March 2026 |
| Group J: 8 April - 22 April 2026 | 12PM 3 April 2026 |
| Group K: 15 April - 29 April 2026 | 12PM 10 April 2026 |
| Group L: 22 April - 6 May 2026 | 12PM 17 April 2026 |
| Group M: 29 April - 13 May 2026 | 12PM 24 April 2026 |
| Group N: 6 May - 20 May 2026 | 12PM 1 May 2026 |
| Group O: 13 May - 27 May 2026 | 12PM 8 May 2026 |
Considerations
When choosing a group, please consider the following in your decision:
- The upgrade does not need to take the full 2 weeks. The upgrade can be completed as soon as you are happy with the UAT branch and you comment back in ticket
- There is no content publishing freeze for the duration of the upgrade
- Only the master branch is updated, all other environments will be deleted during the upgrade process.
(ie the branches will remain in GitLab - only the environments are deleted) - All active development should be finalised and changes merged back to master prior to the cutoff date listed above for your group
- There must be a code development freeze for the duration of the upgrade. All development effort should be focused on the upgrade - reducing the the 2 week timebox
- Configuration management is not available on the D11 upgrade branch