Items to be discussed
Prerelease Content Management Activities:
Content Validation Activities:
MBR has been analysing the Daily Build RVF results for the past few weeks, and working with Peter to clear down the failures. We just, therefore, need to confirm that the RVF report is now:
a) In the Preliminary Handover meeting it is being cleaned on a daily basis, with the intention of having it cleared down completely by the handover on 9th November 2018 - CONFIRMED
b) Clean in the Final Handover meeting (before we version the content)???????? to confirm next week...
ACTION: Maria to share the Content report results with the content team - she will confirm whether or not any fixes are required before the Alpha release on Monday - Maria confirmed all clean now and no further issues requiring action
Final issue found by UK (
Elaine in UK is happy with the plan, they're just waiting for Jeremy Rogers to confirm he's also happy with it...
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, Donna and Yong will all be around to support wherever needed.
Early visibility of Release Notes
Andrew Atkinson has created the template to update on Confluence: SNOMED CT January 2019 International Edition - SNOMED International Release notes - see here with relevant figures replaced with ??????? ready to be replaced with the relevant January 2019 figures
ACTION: Lesley MacNeil and Paul Amos to review and approve once complete...
Discussion of existing Known Issues from the previous Release
|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.|
Mapping: Clean after initial meeting - how are we looking for delivering tomorrow?? Donna all complete and happy, AAT to verify with WCI that they are cracking on with final release files...
|7||Versioning and Change Freeze|
AAT to raise ticket now - DONE
Versioning completed and initial successful builds run - will confirm properly once final validation run after mapping files delivered....
MBR has now been using the Daily Build QA report (which will contain data from the next Release Cycle by the time this Release is published) - https://dailybuild.ihtsdotools.org/qa/
ACTION: Maria Braithwaite will run the spell check and RVF one final time after the cut off is complete... done??
MBR can also now use this for the stats in the Release Notes, as once content cut off is complete, this Daily Build report will show the static version for the July 2018 International Edition.
ACTION: Maria Braithwaite The only thing we need to be careful of here is large updates during Alpha/Beta release cycle - so MHA to run this again after Beta release is complete and update Release Notes if required - done??
No known risks! Everyone comfortable so far...