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:
| MBR has been analysing the Daily Build RVF results for the past few weeks, and working with Peter to clear down the failures. Early Alpha run by AAT 11th 12th May 2021 was mostly clean - we've since resolved all issues found: MBR will share content report with team when it is ready. AAT to re-run the Content Report AFTER the MRCM changes are complete and stable so she can share with team! - COMPLETED on 03/06/21 and Maria & Team signed off on 04/06/21 | ||||||||
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 + Yong + Donna will all be around to support wherever needed
| ||||||||
5 | Early visibility of Release Notes | Andrew Atkinson has created the template to update on Confluence: SNOMED CT July 2021 International Edition - SNOMED International Release notes - content team to update with relevant data for July 2021 content..... ACTION: Maria Braithwaite and Donna Morgan will kindly aim to get them to Andrew Atkinson by 24th May 2021 - done ACTION: Monica Harry and Paul Amos to review and approve once complete - done
| ||||||||
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. | Release:
Mapping (Donna):
Content (Maria): | ||||||||
| ||||||||||
7 | Versioning and Change Freeze | Plan is to follow the new process as defined last cycle: Technical Team Release tasks - July 2021
| ||||||||
8 | Stats Report | MBR has been using the Daily Build QA report for stats and has the information needed for release notes. Release Reports run via the reporting platform: Spell checks: https://docs.google.com/spreadsheets/d/1gQhfVFmoq3_nn0jn36NxUl3Zr_EnORCi5guqt2OZniQ/edit#gid=0 Concepts changed : https://docs.google.com/spreadsheets/d/1yNsemZdWhjl9G69c3Gyhe8FyA9KdrZbVFHGAl8dEJ54/edit#gid=1 Concepts inactivated : https://docs.google.com/spreadsheets/d/1HCdH8JU3td67Sejb3ecS8dQjzkjpma2qqJOKNFmEpoo/edit#gid=0 New components : https://docs.google.com/spreadsheets/d/1NhBWtyu1AYpwmZbuaZaHpM0PtevzT1H6ChpeBY6gc1o/edit#gid=0 Release stats : https://docs.google.com/spreadsheets/d/1tgeiHFIj2BCw4nFMYvlLqmqWN7F0rC8fTs9Y0w31ooc/edit#gid=0 Summary component stats: https://docs.google.com/spreadsheets/d/1jHr_xHWlfkWppwnfK5HZfI6pcSo6Dqx6X_gy7BhVBpE/edit#gid=0 HOWEVER, should we focus on the Summary Component stats report now, as with MS products, in order o ascertain Intention of the authoring cycle vs real data actually contained in the Release files?
| ||||||||
9 | Risks |
| ||||||||
10 | Re-open Authoring | Are we all ready to re-open authoring? (or any outstanding risks)?
|