| Date | Responsibility | Deliverables |
|---|---|---|
| Authoring begins for August 2021 International 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. | |
| | Last day to launch a new task in the authoring platform intended for the current release cycle. | |
| Maria Braithwaite | 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. | ||
| Maria Braithwaite | Lockdown of project promotion. Restart content editing for the next release cycle in the new release branch. | |
| Content team review, rebase and finalise all content | |
| Content team promote to MAIN final content for all projects to be released in the current editing cycle (weekend contingency) | |
| Content Release Lead to request (via Infra ticket) formal lock down of all Projects (i.e. no promotions allowed), except for the Internal QA Project (Internal Quality Assurance - INTQA) - which needs to remain open until from CONTENT CUTOFF DATE in order to allow Content Release Lead to promote all final QA fixes before handover. | |
| Final content review (2 days) Request vet extension report Request QI content changes report Review of new observable entity and evaluation procedure concepts for conflicts with the LOINC agreement | |
|
| |
| Planned Initial Handover meeting | |
|
| |
| termServer branching and Release versioning - Technical Team Release tasks - August 2021 | |
| Andrew Atkinson | Full validation of the initial exported content |
|
| |
|
| |
|
| |
Handover of Release Notes to technical team Release manager (Note: recheck final figures for concept changes/ additions etc before member release and public release to take into account changes made after close of editing). | ||
|
| |
| PLANNED BETA Release date Restart the mapping Drip Feed - this can actually be done earlier than the final Beta if required, as the only pre-requisite is to complete the ICD-0/ICD-10 testing in the Beta build. This is simply to provide confidence that there will not likely be map changes during the Alpha/Beta stage, which could in theory create re-work for the teams. This risk should be balanced against the growing backlog of map changes, and a decision made whether to use an early Beta build to switch the drip feed back on.
| |
| PLANNED BETA feedback deadline | |
| Member Release date | |
| PRODUCTION Public Release date |
Overview
Content Tools
Apps