Page tree

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

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): INFRA-5998 - Getting issue details... STATUS

SNOMED International Release Management Procedure - Versioning and Branching the International Edition

 

WCI (External Team)

MAPPING GENERATION PROCESS - see details here: ....

 

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 Release Manager confirms proposed Production release package:

  • run the test upload into Dev browser to ensure no issues.
  • re-configure the Daily Build + Daily Build browser to work in the next Editing cycle -

 

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...

Development Team to pair with DevOps Team

Once Release Manager confirms Production release is published:

DevOps Team

Once Release Manager confirms Production release is published:

  • No labels