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 Michael 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 10th May 2017
b) Clean in the Final Handover meeting (before we version the content)
ACTION: Michael Chu - to complete fixes for ISRS-279 and ISRS-280 then will re-build Daily Build as clean... - COMPLETE
ACTION: Michael Chu to add new RVF assertions to cover these scenarios in future releases...
ACTION: Michael Chu to finally run another diff report to confirm all SPanish ID clashes are now cleared down by Peter's fix....
ACTION: Michael Chu to open ISRS ticket to track the SPanish ID's through this release and ensure no regression issues...
ACTION: Gabor to complete work onAPDS-408.... - NO LONGER INTERNATIONAL IMPACT, MS ONLY (confirmed by Gabor on 16/11/2017)
ACTION: Andrew Atkinson to therefore run the Content Validation report through on the final cut-off content from 10th November 2017 onwards, in order to identify any outstanding issues and resolve them before 15th November 2017 when the mapping cut off takes place. - COMPLETED
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 2018 International Edition - SNOMED International Release notes - see here with relevant figures replaced with ??????? ready to be replaced with the relevant Jan 2018 figures
ACTION: Lesley MacNeil to review and approve... - done on
Discussion of existing Known Issues from the previous Release
|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.|
See section 2 for current known issues...
|7||Versioning and Change Freeze|
Everyone still fine with all dates on this...
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...
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 2017 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.
No known risks! Everyone comfortable so far...