NOTE ALL DATES PROVISIONAL AND SUBJECT TO CHANGE.
Critical Dates this Cycle:
- 4th September 2023: Public holiday Labor Day (US/Canada)
Date | Time | Responsibility | Deliverables |
|---|---|---|---|
| 18.00 | SI Content Release Lead | Authoring begins for October 2023 International release. Update root concept synonym - TO OCTOBER 2023 (not Sept). Check for and request updates to validation to align with large scale changes to content development (e.g. axiom, GCI, concrete domains etc). Check for MRCM changes to be implemented for the release. SI Content Release Lead to check Daily Build RVF report daily to ensure no failures in the "Traceability Service" assertion(s). These will provide advanced notice of the type of failures we currently don't find until Release time (items missing from the RF2 manifest, package formatting issues, etc), so that they can be fixed well before the release. |
| 12:00 | SI Devops Team | Setup new automated JIRA tickets to be generated from the parent International Release ticket, for all Mapping steps below (both internal and external) |
| 12:00 | SI Content Release Lead | No further batch loads or bulk updates. No further promotion for projects that have large scale changes for example promotion from the Community Content or changes to foundational hierarchies likely to have impact across other content. Cross check that all MRCM changes have been made and the associated content changes completed (i.e. no MRCM errors on Main). No further changes to MRCM. |
| 17:00 | SI Release Manager | Verify with Content Release Lead any new moduleDependency/RefsetDescriptor records required for this cycle...
|
| 17:00 | SI Release Manager |
|
09:00 | SI Content Release Lead | Notify Content Team about forthcoming release close and aim to complete project promotion in advance of cut off to prevent last minute issues for the Mapping Team. | |
| 12:00 | SI Content Release Lead | Last day for the Content team to promote any changes intended for release in the current editing cycle. 12.00 UTC - CONTENT CUT OFF - Final project promotion Content team may continue to author after final project promotion and until the authoring platform is under maintenance window, but must not delete any new concepts or components that have already been promoted for the March 2023 release. No project promotion until further notice. Submit INFRA ticket for project promotion to be disabled in the authoring platform until further notice. | |
| 14.00 | SI Release Team | Initial handover meeting - once all signed off, full validation of initial content + fixing of all issues that it is possible to resolve before versioning (cannot move this meeting earlier as Content Release Lead needs enough time to run full validation after cut-off before this handover meeting) | |
| 00:01 - 05:00 | WCI |
|
| 09:00 | SI Mapping Team | Mapping team to finalise any mapping from the final content promotion after the 12:00 content cut off previous day (or any issues identified during the Mapping Server validation process), and then Resolve their "Mapping Complete" ticket to confirm that "Mapping QA complete". NB: this is using the content from yesterday's final promotion cut off at 12:00, as the Daily Build feed then ran at 01:00 | |
| 09:00 | SI Content Release Lead | Final content review and validation in the current release branch:
| |
| 09:00 | SI Release Manager | Check that SEP + lateralizable refset generation process has been run before kicking off test build(s). |
| 12:00 | SI Mapping Team | 12:00 - MAPPING CUTOFF (This is using the content from last night's Daily Build feed (run at 01:00)) | |
| 12:00 | SI Content Release Lead |
| |
| 12:00 | SI Release Manager | For the first few releases the SI Release Manager should run an initial full Release against the UN-VERSIONED content, to ensure no failures in the "Traceability Service" assertion(s) in the RVF report. These will provide advanced notice of the type of failures we currently don't find until Release time (items missing from the RF2 manifest, package formatting issues, etc), so that they can be fixed well before the release. Versioning to proceed once SI Release Manager confirms that there are no Critical issues in this build. ***** NOTE there will be some false positives in the new Traceability Assertions (assertionUuid: "b7f727d7-9226-4eef-9a7e-47a8580f6e7a") until the map files can be finalised and uploaded to the termserver (see below) the number of failures should exactly match the number of records across BOTH map file delta's - so if this is the case these can be ignored until the map files are uploaded to the termserver in a few days... |
| 16.00 | SI Devops Team | If any Critical fixes have been required, we need to:
|
| 15:00 | SI Release Team | Final handover meeting - final cross check to ensure that all Release validation complete, and any last minute tasks (refset generation, final Mapping updates from last night's drip feed, etc) are complete before versioning green lit. |
| 12:00 - 17:00 | SI Devops Team | Technical team release tasks (as and when initial validation is signed off at each milestone)
| |
| 09.30 | SI Release Manager | New versioned Release Build (including both ICD-0 + ICD-10 maps from termServer) is created and validated by SI Release Manager ******************************************************************************************************************************************* THIS BUILD MUST BE DONE WITH x PREFIXES REMOVED + USING PRODUCTION NAMING CONVENTIONS SO DEVOPS CAN USE IT ******************************************************************************************************************************************* ***** MANIFEST CHANGED TO PULL MAP FILE DATA FROM SNOWSTORM INSTEAD OF EXTERNALLYMAINTAINED FOLDERS ****** | |
| 18:00 | SI Release & Devops teams | Update the devops Report ticket with the relevant 2x release packages so there's no confusion, PLUS DevOps to run new SCS Report (eg)
| |
| 18:00 | SI Content Release Lead | Approximately 18.00 UTC - AUTHORING + MAPPING RE-COMMENCE Restart content editing for the next release cycle in the new release branch on authoring platform. Project promotion is also clear to commence from this point onwards. Maria Braithwaite SEND NOTICE to Content team members - all existing tasks must be rebased to prevent problems with the classification (until we can automate all rebases then rebasing the tasks is also needed. Dev Ops will still rebase all projects each release). Mapping Drip Feed switched back on (but mapping tool will not be back up to date until first drip feed run later tonight). | |
| 01:00 - 09:00 | WCI (AUTOMATED) |
| |
| 09:00 | SI Mapping Team | Re-start International Mapping work for the next cycle. | |
| 09:00 | SI Release Manager SI Mapping Team WCI | DR PLAN: If there is a Critical (P1) issue found in either the Map files or the final SNOMED CT content (shouldn't be due to the new task/project validation, but we need an emergency process just in case), then WCI can import a specific fix branch straight into the Cloned Release Mapping Server, without bleed through from the next month's content. However, this should only be used in the genuine emergency situations... |
| 13.00 | SI Release & Devops teams | Once Final, versioned Release Build is signed off by SI Release Manager, it is handed over to DevOps to update the Daily Build, plus all AP validations, etc As this can take a few hours or even more, in the interim DevOps will use the provisional Snapshot release from the versioning process in order to ensure minimal downtime for these services. | |
- | 09:00 | SI Release Manager SI Content Release Lead | Full manual + automated validation of the versioned content. Lateralizable and SEP ref sets. (BUT ONLY IF NEW AUTOMATION OF THESE REFSETS IS STILL NOT YET AVAILABLE). |
- | 09:00 | SI Content + Mapping Teams | Preparation of release notes. |
| 12:00 | SI Content Release Lead | Handover of release notes to SI Release Manager. | |
| 09:00 | SI Release Manager | Build final Production release for October 2023. Run full regression testing and fix any subsequent issues. |
| 17:00 | SI Release Manager | As early as possible, send DevOps the final PROD Release package, to upload into the Browser, etc in readiness for the Release day (the data will remain hidden within the browser until 1st of the month at 00:01) |
| 17:00 | SI Release Manager | PRODUCTION RELEASE to community
| |
| 09:00 | SI Devops Team | Once Release Manager confirms Production release is published:
|
Team notifications:
| Team | Stakeholders to notify |
|---|---|
| SI Release Manager | |
| SI Content Release Lead | |
| SI Devops Team | |
| SI Content Team | |
| SI Mapping Team | |
| WCI |