...
Date | Responsibility | Action / Deliverables | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DevOps Team | Maintenance screen to be raised in Production once Content Release Lead confirms content cut off is complete (they will request this via "Infra" JIRA ticket) | ||||||||||
| Development Team | Traceability content verification - Checks to be completed in order to ensure that there are no concepts in the termserver that were promoted by the authors, but yet somehow didn’t make it into MAIN ready for versioning (as has happened before) USE THE NEW AUTOMATED TRACEABILITY REPORT once it's in Prod. In the meantime, Kai will run this manually each cycle to confirm traceability is clean... | ||||||||||
- | DevOps Team | Termserver branching and Release versioning (DevOps to raise tickets themselves as per Terance's request): | ||||||||||
| WCI (External Team) | MAPPING GENERATION PROCESS - still in review... | ||||||||||
| DevOps Team | Provisional date to drop Maintenance screen and re-open Content authoring for next editing cycle - UPDATE DATE IN FUTURE IF WE DECIDE WE CAN LET THE AUTHORS BACK IN EARLY | ||||||||||
| DevOps Team | Once authors confirm Editing has re-commenced:
Performing this step early allows the daily build to report on the next monthly release content, for both authoring validation and external use. New unreleased content will hidden in the main browser until the effectivetime. If any content has to be removed due to urgent issues we will need to back-out and reimport the International data. | |||||||||||
| Development Team | Once Release Manager confirms Production release is published, update both the
Check this through with Peter as likely unnecessary now with new reports... | ||||||||||
NOT REQUIRED FOR MONTHLY RELEASES | Once Release Manager confirms Production release is published:
| |||||||||||
| DevOps Team | Once Release Manager confirms Production release is published:
|
...