Date | Deliverables | ||
---|---|---|---|
| Authoring begins for the January 2019 International Edition editing cycle. | ||
06 | Andrew to retrospectively add in the final confirmed Public release MRCM UUID's back into the MRCM master sheet, to allow Linda to start her maintenance work |
| Content team to deliver final MRCM change requests to Linda for action |
17 Aug | Linda delivers MRCM changes to content team for review - Content Team to complete this by 24 Aug 24 Aug | ||
| Content team to deliver final reviewed MRCM changes plus any feedback to Linda | ||
27 Aug | Linda to make any necessary changes (based on feedback from the authors) - Linda to complete this (and verify with Yong) by 30 Aug | ||
31 Aug | NO FURTHER MRCM CHANGES ACCEPTED - everyone has agreed this, with the caveat that any critical changes can be reviewed by all of us in order to analyse impact vs business case and allow a change if absolutely necessary. | ||
03 |
| ||
05 |
| ||
19 |
| ||
|
| ||
| 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 - 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) Review of new observable entity and evaluation procedure concepts for conflicts with the LOINC agreement. | ||
|
| ||
|
| ||
|
| ||
|
| ||
|
| ||
Handover of Release Notes to technical team Release manager (Andrew) | |||
| PLANNED Alpha Release date | ||
| PLANNED Alpha feedback deadline | ||
| PLANNED BETA Release date | ||
| PLANNED BETA feedback deadline | ||
| Member Release date | ||
| Public Release date |
...