Agenda
Items to be discussed | Actions | |
|---|---|---|
| 1 | Prerelease Content Management Activities:
|
|
| 2 | Discussion of existing Known Issues from the previous Release |
|
| 3 | Content Validation Activities in the Current Release cycle:
***** AS OF NEXT MONTH's RELEASE (October 2021), THIS MANUAL VALIDATION SHOULD HOPEFULLY HAVE BEN REPLACED BY INCREASED SCOPE OF AUTOMATED VALIDATION, AND THEREFORE THIS STEP CAN BE CHANGED TO SOMETHING LIKE "Content Release Lead confirms to Release Manager that all Projects had full automated validation run against them, and all issues identified were resolved before promotion." ***** | Maria has completed all these manually for this cycle, but this will slowly change to automated validation in the upcoming releases... |
| 4 | Content Team Support availability - Confirm which members of the content team will remain on stand-by until clean database milestone is achieved after release build file QA and post-release assertions are validated. | Maria and Yong will be around.
|
| 5 | Early visibility of Release Notes | Andrew Atkinson has created the template to update on Confluence: SNOMED CT September 2021 International Edition - SNOMED International Release notes - content team to update with relevant figures for July 2021 content..... ACTION: Maria Braithwaite and Donna Morgan confirmed we don't need these for the September and October releases - instead they'll just log the change notes in their Trello board and add them into the Jan 2022 release when we get to it. Yong and Linda to confirm whether or not we need to add info on the new metadata concepts.... QUESTION: Do we need a more streamlined format? Or just include a lot less data? - WE'LL PLAY AROUND WITH THIS IN THE NOVEMBER RELEASE - WE SHOULD GO VERY MINIMALIST AND THEN SEE WHO (if anyone) in the community complains about it, and ask them to tell us specifically what hey want us to add back in... ACTION: Monica Harry and Paul Amos to review and approve once complete
|
| 6 | Brief run through of the known issues already identified by the content team during the QA batch process, to ensure that technical team are aware of them, and can either resolve them in time for the release, or confirm as known issues. | Maria confirmed all tickets complete. |
| 7 | Versioning and Change Freeze | Plan is to follow the new processes as now defined: AAT walked through and agreed new process with DevOps already, so unless there are any further questions/issues??
Versioning + related issues complete and resolved as of = + |
| 8 | Stats Report | 3 Sept 2021 Reports run (by Maria) via the reporting platform: Inactivated concepts https://docs.google.com/spreadsheets/d/1gpG9sxbw1bL0LAkP90iXPr7FffvjibRUMT3VZk6R3xU/edit#gid=0 Inactivated concepts in ref sets https://docs.google.com/spreadsheets/d/153l9z-I-8IHb0dFQgu6B-1mKMFyByxQJAKf8m4EFaOA/edit#gid=0 New and changed components https://docs.google.com/spreadsheets/d/1LzeZcHFWYJUFUGS8RjpTrP0eMM9N7LkTjXc6gyLKvZo/edit#gid=0 New descriptions https://docs.google.com/spreadsheets/d/1u6GEw8lAeNFgHV1Nk7e1HDdXVFhH2mJeXAg7krTiVRk/edit#gid=0 Release stats https://docs.google.com/spreadsheets/d/1oonFtGRtdCEx8lNE2jOaOTkAT0nhm2ahCjIYA5LWN0c/edit#gid=0 Summary component stats https://docs.google.com/spreadsheets/d/11bMMJL2LTMMW90k-7Mn6HRg0O6BXvgxn1B201cEYxsM/edit#gid=0 Peter confirmed reports will not be updated now, as most are based on Delta's, and once we've versioned the Delta files will be empty! So we need to check the original reports run by Maria (above) straight after her authoring checks were complete, and just manually take all of the latest fixes (like ISRS-921 - Getting issue details... STATUS , etc) into account. |
| 9 | Risks | Just the obvious 8.4 release happening at the same time as Versioning... |
| 10 | AOB |
900000000000441003 SNOMED CT Model Component (metadata) (metadata) Unexpected Inf Rel Module Y Y/Y Concept module 900000000000012004 vs Rel module 900000000000207008 [I0] 116680003 |Is a (attribute)| -> 138875005 |SNOMED CT Concept (SNOMED RT+CTV3)| Checked with Yong - I think this is a known issue about module dependency. 138875005 |SNOMED CT Concept (SNOMED RT+CTV3)| belongs to the 900000000000207008 |SNOMED CT core module (core metadata concept)|. But its subconcepts include |SNOMED CT Model Component (metadata)| and |SNOMED CT model component module (core metadata concept)| and |SNOMED CT core module (core metadata concept)| are all belong to 900000000000012004 |SNOMED CT model component module (core metadata concept)|.
|