...
| Date | Responsibility | Deliverables | ||||
|---|---|---|---|---|---|---|
| Authoring begins for November 2021 International release. Check for and request updates to validation to align with large scale changes to content development (e.g. axiom, GCI, concrete domains etc). Content Release Manager 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. | |||||
| 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. Create the module dependency records for the next release. | |||||
Last day for the Content team to promote any changes intended for release in the current editing cycle. Content review for conflict with LOINC agreement. Final project promotion 12.00 UTC. Content team may continue to author after final project promotion and until the authoring platform is under maintenance window, but must not delete any concepts or components that have already been promoted for the November 2021 release. No project promotion until further notice. | ||||||
| Release Team | 12:00 - (October/November INT Releases ONLY) - DOUBLE CHECK THAT SEP + LATERALIZABLE REFSET GENERATION PROCESS HAS BEEN RUN BEFORE KICKING OFF TEST BUILD(s) | ||||
12:00 - Content release manager final content review and validation in the current release branch:
| ||||||
WCI | Mapping Generation process (ICD-0 + ICD-10) - November 2021 12:00 - Mapping team to finalise any last mapping from the final content that came through after 12:00 content cut off yesterday(or any issues identified during the Release Mapping Server validation process), and then Resolve their "Mapping Complete" ticket to confirm that "Mapping QA complete". 12:00 30 - MAPPING CUTOFF | |||||
Content Release Leads | 12:30 - SI Content Team to create 2x new Tasks in snowStorm, to accept the upload of the new Map files Delta's (one for SimpleMap + one for ExtendedMap delta files) | |||||
WCI (Rick Wood) | Mapping Generation process (ICD-0 + ICD-10) - November 2021 NB The mapping process will use the content from | todayLAST NIGHT's final | promotion lockdown at 12:00, as the Daily Build feed will run later tonight at 01:00 UTC02:00 UTC - (or immediately after the Daily Build/Snapshot provided by DevOps post-versioning is available Daily Build (at 01:00). This means that in theory something could slip through and remain unmapped, IF it's authored after the final Daily build and before the Content Cut Off (ie) between 01:00 - 12:00.
| Release Mapping Server needs to have SNOMED completely removed + the latest version re-uploaded.
| ||
| Release Team | 14:00 - For the first few releases the 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 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 - Initial handover meeting - once all signed off, full validation of initial content + fixing of all issues that it is possible to resolve before versioning. | |||||
| ?16:00? - Build of the final, Versioned Build + regression testing | ||||||
17:00 - If any Critical fixes have been required, we need to:
| ||||||
| WCI (Rick Wood) |
| ||||
| 11:00 - Final handover meeting - final cross check to ensure that all 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 - Technical team release tasks (as and when initial validation is signed off at each milestone)
Reminder to WCI to cut off mapping drip feed (but NOT clone over to Release Server until Mapping Team confirms that both ICD-0/ICD-10 + GMDN maps are all updated based on Content + latest GMDN content. | ||||||
If there are any risks of the Content changing between now and the Published Production release at the end of the month, we need to request Clone of Mapping content (both ICD-0/ICD-10 + GMDN) over to the Release Server, in order to provide a stable baseline for both upcoming International + GMDN releases:
Backup plan: If there is a Critical (P1) issue found in the final 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... | ||||||
New versioned Release Build is created and validated by Release Manager ***** MANIFEST MUST BE CHANGED TO PULL MAP FILE DATA FROM SNOWSTORM INSTEAD OF EXTERNALLYMAINTAINED FOLDERS ****** | ||||||
| Once Final, versioned Release Build is signed off by Release Manager, it is handed over to DevOps to update the Daily Build, plus all AP validations, etc | ||||||
| Maria Braithwaite | ?16:00? - Restart content editing for the next release cycle in the new release branch on authoring platform. 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). | |||||
WCI (Rick Wood) |
| |||||
- | 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). | |||||
- | Preparation of release notes. (NOT REQUIRED FOR NOVEMBER 2021 RELEASE). | |||||
| Handover of release notes to Technical release manager. (NOT REQUIRED FOR NOVEMBER 2021 RELEASE). | ||||||
- | Share with external stakeholders for pre-Production release sent to relevant stakeholders for final review, plus fixing + regression testing of all issues identified. | |||||
| Andrew Atkinson | Production internal release date. |
...