...
Date | Responsibility | Deliverables | |||
---|---|---|---|---|---|
| Authoring begins for frequent delivery migration for the 2021 International release. 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. | ||||
03 | 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. | ||||
17 Aug | Last day to launch a new task in the authoring platform intended for the current release cycle. | ||||
18 Aug | 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. | |||
19 Aug | Lockdown of project promotion via INFRA ticket. Planned initial handover meeting (if required). Restart content editing for the next release cycle in the new release branch. No project promotion until notified by Technical team. | Maria Braithwaite | Content release manager final content review and validation in the current release branch:
| ||
Handover of content to Technical team release manager. | |||||
| |||||
-01 | Final handover meeting - once all signed off, full validation of initial content + fixing of all issues that it is possible to resolve before versioning | ||||
01 -03 | Content team - no access to authoring platform 6 and 7 September. 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. | ||||
- | Donna Morgan | Mapping Team to notify WCI mapping/review ready for QA. QA of mapping (Mapping Team + WCI). | |||
Terance Shird | termServer branching and Release versioning. | ||||
(if possible on the same day as 8.4 Release to give us a clean baseline for the new Traceability service - if not possible then 8.4 release on 6th, and versioning on 7th) | |||||
- | WCI | MAPPING GENERATION PROCESS - still in review... | |||
Maria Braithwaite | Restart content editing for the next release cycle in the new release branch on authoring platform version 8.3 | ||||
- | - | 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). | |||
06 Aug -10 Aug | Mapping QA complete. Preparation of release notes. | ||||
Mapping team 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. Handover of ICD-0 + ICD-10 maps to technical team Release manager (Andrew Atkinson) Restart the mapping Drip Feed. | |||||
(NOT REQUIRED FOR SEPTEMBER or OCTOBER 2021 RELEASES) | |||||
10 Aug | Maria Braithwaite | Handover of release notes to Technical release manager. | 20(NOT REQUIRED FOR SEPTEMBER or OCTOBER 2021 RELEASES) | ||
- | 27 Pre | IF Release leads are confident in the quality of September release then 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. |
...