Date | Time (UTC) | Responsibility | Action / Deliverables |
|---|---|---|---|
| 12:00 | Devops | Setup new automated JIRA tickets to be generated from the parent International Release ticket, for all Mapping steps below (both internal and external) |
| 23:00 | SI Release Team | 23:00 (or whenever Project Promotion is confirmed as locked down) - Technical team Release Manager to send request to WCI for preview Mapping files (ICD-0/ICD-10 only), for use in the pre-versioning validation Build first thing in the morning | |
| 12:00 | SI Mapping Team WCI (External Team) | MAPPING CUTOFF This is using the content from last night's final promotion lockdown at 23:00 UTC, as the Daily Build feed runs at 01:00 UTC. |
| 12:00 | SI DevOps Team | Snapshot used to provisionally bring the AP validation etc back up again today, so that it works for the interim period until the new Production release package is signed off tomorrow (on the 15th October this cycle)... |
| 16:00 | WCI (External Team) | *** DRIP FEED SUSPENDED from this point onwards (planned for today + tomorrow only) *** |
| 02:00 | WCI (External Team) | Cron job to completely remove SNOMED + upload the latest version to the Release Mapping Server. In future, this should happen immediately after the Daily Build/Snapshot provided by DevOps post-versioning is available, if Rick Wood can automate this? |
| 03:00 | WCI (External Team) | WCI to validate the Release Mapping Server |
| 04:00 | WCI (External Team) | WCI to lift maintenance window and allow Mapping Team to access other projects ONLY (GMDN, MedDRA, etc) |
| 09:00 | SI Mapping Team | Mapping team to finalise any last mapping from the final content that came through last night, and then Resolve their "[month] Mapping Complete" JIRA ticket |
| 10:00 | WCI (External Team) | If there are any risks of the Content changing between now and the Published Production release at the end of the month, we need to request Clone of Mapping content (both ICD-0/ICD-10 + GMDN) over to the Release Server, in order to provide a stable baseline for both upcoming International + GMDN releases. |
| 12:00 | Devops | Manual/automated backup of Mapping Server Chris Morris to automate when possible... |
| 13:00 | WCI (External Team) | Mapping Server Cloned over to the Release Mapping Server Rick Wood did you say this needs a new server or you can re-use existing release server? In future, this should happen immediately after the backup of the Mapping Server is complete, if this can be automated? |
| 15:00 | WCI (External Team) | ICD-0 + ICD-10 map files are then generated by WCI and QA reports checked Potential for some discussion with Donna if any red flags in these reports... |
| 17:00 | WCI (External Team) | ICD-0 + ICD-10 map files sent to technical team Release manager (Andrew Atkinson) before close of play |
| 18:00 | WCI (External Team) | *** Mapping Drip feed is restarted *** |
| 02:00 | Automated | Mapping Drip feed runs for the first time since the initial cut off. |
| 09:00 | SI Mapping Team | SI Mapping Team are able to re-start work for the next cycle |
| 09:00 | SI Release Team | Technical team Release manager builds and validates a new Pre-Production release based on the new ICD-0 and ICD-10 files. |
| 15:00 | SI Release Team | Once Final, versioned Release Build is signed off by Release Manager, it is handed over to DevOps to update the Daily Build, plus all AP validations, etc As this can take a few days (depending on when the weekends fall this cycle, etc), in the interim DevOps will use the provisional Snapshot release from the versioning process in order to ensure minimal downtime for these services. |
| 09:00 | Everyone | DR PLAN: If there is a Critical (P1) issue found in either the Map files or the final SNOMED CT content (shouldn't be due to the new task/project validation, but we need an emergency process just in case), then WCI can import a specific fix branch straight into the Cloned Release Mapping Server, without bleed through from the next month's content. However, this should only be used in the genuine emergency situations... |
Overview
Content Tools
Apps