SNOMED International Release Management

Page tree

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

Compare with Current View Page History

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

 

Release Team

For the first few releases the Release Manager should run an initial full Release against the UN-VERSIONED content, to ensure no failures in the "Traceability Service" assertion(s) in the RVF report.  These will provide advanced notice of the type of failures we currently don't find until Release time (items missing from the RF2 manifest, package formatting issues, etc), so that they can be fixed well before the release.  

Versioning to proceed once Release Manager confirms that there are no Critical issues in this build.

 

DevOps Team

Termserver branching and Release versioning (DevOps to raise tickets themselves as per Terance's request): INFRA-7395 - Getting issue details... STATUS

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

 

WCI (External Team)

MAPPING GENERATION PROCESS - still in review...

 

DevOps Team

*** Maintenance screen to be lifted in Production ***

Provisional date to drop Maintenance screen and re-open Content authoring for next editing cycle - providing no Critical issues identified...


DevOps Team

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

Development Team to pair with DevOps Team

NOT REQUIRED FOR MONTHLY RELEASES

Once Release Manager confirms Production release is published:

DevOps Team

Once Release Manager confirms Production release is published:

  • Update all Production systems (authoring platform, browser) using the final S3 published package.
  • This needs to include the new Release Stats page in the browser (https://browser.ihtsdotools.org/qa/#/descriptive-statistics), which can be updated using step 7 ("If this is the final INT release we need to also update the Stats") in these instructions:  https://confluence.ihtsdotools.org/display/DEVOPS/Browser+Release+Updates
    • NOTE:  For the initial soft launch Releases this will just be tested in Dev/Uat browser rather than Prod to avoid confusing users
  • From September 2020 ensure that the GPS ValueSet is available through the FHIR API ie https://browser.ihtsdotools.org/fhir/ValueSet/gps
  • No labels