...
Date | Responsibility | Deliverables | |
---|---|---|---|
| Authoring begins for October 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). Daily Build to be continuously checked by Content Release Lead(s) 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. | ||
| 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. | Maria Braithwaite||
Last day to launch a new task in the authoring platform intended for the current release cycle. | 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 23: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 October 2021 release. No project promotion until further notice. | ||
| 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. | ||
12:00 - Technical team release tasks (as and when initial validation is signed off at each milestone) termServer branching and Release versioning 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. | |||
Maria Braithwaite | ?16:00? - Restart content editing for the next release cycle in the new release branch on authoring platform. | ||
WCI | Mapping QA complete. MAPPING CUTOFF DATE (12:00 UTC)
15th October:
16th October:
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... | ||
- | 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 OCTOBER 2021 RELEASE). | ||
Handover of release notes to Technical release manager. (NOT REQUIRED FOR OCTOBER 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. |
...