LESSONS LEARNT FROM OCTOBER:
- We need to switch off the auto-message regarding the Drip Feed being switched off just after the content cut off at 23:00 - this causes disruption yet the drip feed still appears to run! WCI investigating....
- We need to strongly consider bringing the Content Cut Off forward to 12:00 the previous day - Maria agreed, so this will form part of the November 2021 schedule...:
- a) The handover to WCI was too fraught, with no confirmation of clean content cut off
- b) There was not enough time to run the SEP + Lateralizable refset generation process, in order to get the Provisional Pre-Prod release run the next morning, before the 12:00 Versioning cut off
- c) This way we can run the Final Handover meeting the day of the cut off (at say 12:00), and everyone can be on the same page with respect to the plan for the next day)
- d) We can also then run final content cross checks, ensuring that Maria no longer has to get up at 6am the next day to run them all through!
- e) The last promotion was naturally 12:00 that day anyway (in October), and so there was no business case to keep it open until 23:00
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 11.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. | ||
23:00 - AAT to send request to WCI for preview Mapping files (ICD-0/ICD-10 only), for use in the pre-versioning validation Build first thing in the morning | ||
| Release Team | 09:00 - (October/November INT Releases ONLY) - DOUBLE CHECK THAT SEP + LATERALIZABLE REFSET GENERATION PROCESS HAS BEEN RUN BEFORE KICKING OFF TEST BUILD(s) |
| Release Team | 09: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. |
09:00 - Content release manager final content review and validation in the current release branch:
| ||
| 10:00 - Final handover meeting - once all signed off, full validation of initial content + fixing of all issues that it is possible to resolve before versioning. | |
11:00 - If any Critical fixes have been required, we need to:
| ||
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. | ||
?16:00? - Build of the final, Versioned Build + regression testing | ||
Maria Braithwaite | ?16:00? - Restart content editing for the next release cycle in the new release branch on authoring platform. | |
WCI | Mapping Generation process (ICD-0 + ICD-10) - November 2021 Mapping QA complete. MAPPING CUTOFF DATE (12:00 UTC)
16th November:
17th November:
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... | |
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 | ||
- | 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. |