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 | Check that inferred relationship coming from Snomed Release Service match those in Snowstorm to avoid large and unnecessary data reconciliation effort. |
| Development Team |
Can be removed as soon as improvements in AP 6.7.0 (to automate these checks in the RVF) are successful... |
Development Team | 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) | |
| Infrastructure Team | termServer branching and Release versioning: |
| Infrastructure Team | Once the mapping team have finalised the maps, update the Daily Build/Mapping Drip feed |
| Infrastructure Team | Provisional date to drop Maintenance screen and re-open Content authoring for next editing cycle |
| Infrastructure Team | Once 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 would have been found until too late in the Release cycle. |
Infrastructure Team | Create 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 Team | Once Release Manager sends proposed Beta release package, run the test upload into Prod browser to ensure no issues. |
| Infrastructure Team | Once Release Manager sends proposed Member release package, run the test upload into Prod browser to ensure no issues. |
Infrastructure Team | Create 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 |
|
| Development Team | Once Release Manager confirms Production release is published, update both the
|
| Development Team | |
| Infrastructure Team | Once Release Manager confirms Production release is published, update all Production systems (browser, website, etc) using the final S3 published package. From September 2020 ensure that the GPS ValueSet is available through the FHIR API ie https://browser.ihtsdotools.org/fhir/ValueSet/gps |