SNOMED International Release Management

Page tree

Versions Compared

Old Version 9

changes.mady.by.user Chris Morris

Saved on

compared with

New Version 10

changes.mady.by.user Andrew Atkinson

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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):

Jira
serverIHTSDO JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdb202d822-d767-33be-b234-fec5accd5d8c
keyINFRA-5998

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

 

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

29


DevOps Team

Once Release Manager confirms proposed Production release package: Andrew Atkinson this step should be done once authors are back in (so on the 8th). This way the daily build is reporting authors confirm Editing has re-commenced:

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

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

we had to remove

any content has to be removed due to urgent issues we

would also

will need to back-out and reimport the

Int data.
  • 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 - Browser Daily Build Process

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

    Development Team to pair with DevOps Team

    NOT REQUIRED FOR MONTHLY RELEASES

    Once Release Manager confirms Production release is published:

    • Merge any and all Feedback fixes back into MAIN (eg)
      Jira
      serverIHTSDO JIRA
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverIdb202d822-d767-33be-b234-fec5accd5d8c
      keyINFRA-5438
    • Export changes as delta and import into INTQA project for current authoring cycle

    • Merge fixes down into MAIN at point of versioning
      https://prod-snowstorm.ihtsdotools.org/snowstorm/snomed-ct/swagger-ui.html#!/Admin/promoteReleaseFixUsingPOST

    • Ask the content team to verify everything is as expected in MAIN, according to their intentions when authoring the fixes (outstanding)

    		DevOps Team

    Once Release Manager confirms Production release is published:

    ...