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

« Previous Version 2 Next »

Date

Responsibility

Action / Deliverables

 

Infrastructure Team

Maintenance screen to be raised in Production once Content Release Lead confirms content cut off is complete (they will request this via Infra ticket)

 

Development Team

Run MRCM Validator manually, in order to verify MRCM Refsets themselves (content is now automatically validated against the MRCM as part of RVF).

Michael Chu please confirm if we can now automate this, or at least handover to Release Team to run manually?

 

 

Infrastructure Team

termServer branching and Release versioning:

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

 

Infrastructure TeamOnce the mapping team have finalised the maps, update the Daily Build/Mapping Drip feed

 

Infrastructure TeamProvisional date to drop Maintenance screen and re-open Content authoring for next editing cycle

 

Infrastructure TeamOnce Release Manager sends proposed Alpha release package, run the test upload into Prod browser to ensure no issues.

 

Rory / Infrastructure Team ?Run a classification of a new, clean US project in order to double check there are no classification results. In the past this has identified issues that otherwise wouldn't have been found until too late in the Release cycle.

Infrastructure TeamCreate a new, separate version of the browser with the provisional Beta release package as a baseline. This is to allow the Content Team to verify that all of the Alpha fixes have been applied correctly, & haven't had any adverse impacts.

 

Infrastructure TeamOnce Release Manager sends proposed Beta release package, run the test upload into Prod browser to ensure no issues.

 

Infrastructure TeamOnce Release Manager sends proposed Member release package, run the test upload into Prod browser to ensure no issues.

Infrastructure TeamCreate a new, separate version of the browser with the provisional Member release package as a baseline. This is to allow the Content Team to verify that all of the Alpha + Beta fixes have been applied correctly, & haven't had any adverse impacts.

 

Development Team

Merge all Alpha/Beta fixes into the original Release branch

OLD PROCESS (Kai Kewley / Michael Chu please confirm new SnowStorm process?):

  • Export Release feedback fixes from main/RFJ branch

  • Import Release feedback fixes into the MAIN/[release date]/[fix branch]

  • Promote Fix branch to Release branch for Release Manager to run Production release build

  • Build and test Production release
    a) If all clean then use the new Release branch for final Production Public release
    b) If major issues then revert back to Fix branch for final Production Public release

  • XXX AMI update no longer required XXX

  • Dev-Ops create a new Snapshot export from MAIN/[release date] in Prod termServer

  • Dev-Ops update the classification service using the snapshot export

  • Compare release fixes with MAIN delta export to create a consolidated RF2 delta

  • Import RF2 delta into MAIN/[release date]/[fix branch]

  • Run classifications and validation before promoting MAIN/[release date]/[fix branch] into MAIN

 

Development Team

Once Release Manager confirms Production release is deployed to S3, RVF auto-scaling images to be rebuilt

Michael Chu please confirm new SnowStorm process - is this still required?

 

Development Team

Once Release Manager confirms Production release is published, update both the

 

Development Team

Once Release Manager confirms Production release is published:

  • Merge any and all Feedback fixes back into MAIN (eg) INFRA-4790 - Getting issue details... STATUS
  • Ask the content team to verify everything is as expected in MAIN, according to their intentions when authoring the fixes

 

Infrastructure Team

Once Release Manager confirms Production release is published, update all Production systems (browser, website, etc) using the final S3 published package.

  • No labels