SNOMED International Release Management

Page tree

Versions Compared

Old Version 13

changes.mady.by.user Andrew Atkinson

Saved on

compared with

New Version 14

changes.mady.by.user Maria Braithwaite

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Date of Initial Handover meeting: 13th May 2022

Date of Final Handover meeting: 17th May 2022

Attendees


Page properties


Handover Status

Status
colourRed
titleINITIAL HANDOVER COMPLETE




Agenda


 

Items to be discussed

Actions

1

Prerelease Content Management Activities:

  1. Inactivate the root concept synonym referencing previous release, and add synonym to reference current release.
  2. Update copyright date on synonym (January releases only)
  3. Generate + Validate SEP Refsets
  4. Generate + Validate Lateralizable Refset


  1. MBR - changed manually in this task ORPHANET-3042 verified new description is present 13 May.
  2. MBR - not required as only required in January releases...
  3. Process has generated the data -  pre-close of editing report 13 16 May 2022

    1. https://docs.google.com/spreadsheets/d/1pfmCEgvzflB8ZikxKEK5jJZufjDDuOMMYe2h6jZ0cHE1L07R3BmtohtBX6UY1rCN3F7GaHKLbDgBPaCE34If0Jk/edit#gid=1

  4. Process has generated the data - pre-close of editing report 13 16 May 2022

    1. https://docs.google.com/spreadsheets/d/1pfmCEgvzflB8ZikxKEK5jJZufjDDuOMMYe2h6jZ0cHE1L07R3BmtohtBX6UY1rCN3F7GaHKLbDgBPaCE34If0Jk/edit#gid=2

2

Discussion of existing Known Issues from the previous Release

  1. INFRA-8402 / FRI-376 - RefsetDescriptor - AAT TO TRIAL NEW EXCLUDE REFSET MEMBERS PARAMETER IN THIS RELEASE

  2. Mapping failures checked by Donna and then exceptions listed 

    Jira
    serverIHTSDO JIRA
    serverIdb202d822-d767-33be-b234-fec5accd5d8c
    keyINFRA-8874

  3. Jira
    serverIHTSDO JIRA
    serverIdb202d822-d767-33be-b234-fec5accd5d8c
    keyINFRA-8675
     May ticket for failed traceability assertions 
    Jira
    serverIHTSDO JIRA
    serverIdb202d822-d767-33be-b234-fec5accd5d8c
    keyINFRA-8889

3

Content Validation 

  1. Instead of usual manual Content validation, we now just need confirmation that all Projects had automated validation run against them, and were clean before promotion.
  2. New Issues identified by the community from the previous Monthly Release.
    1. Decision on whether to fix the issues:
      1. VERY QUICKLY in time for this upcoming release?
      2. In good time for the next monthly release?


  1. Content Release Lead confirms to Release Manager that all Projects had automated validation run against them, and all issues identified were resolved before promotion - MBR confirmed all done 
  2. Still have traceability failures: All components in the branch traceability summary must also be in the RF2 export. All components in the RF2 export must also be in the branch traceability summary. confirmed false positives see 
    Jira
    serverIHTSDO JIRA
    serverIdb202d822-d767-33be-b234-fec5accd5d8c
    keyINFRA-8675
    May ticket for failed traceability assertions all false positives 
    Jira
    serverIHTSDO JIRA
    serverIdb202d822-d767-33be-b234-fec5accd5d8c
    keyINFRA-8889
4Mapping schedule

Chris/Rick confirmed today that we now have the new automated process up and running for this release cycle - Maria confirmed she'd had a run through from the team, and so is ready to run the process this cycle... Chris to create an automated JIRA ticket (off the master INT Edition ticket) to remind them to schedule the relevant job(s) over the weekend.  Notifications set to be auto-sent to AAT + Maria...

Maria to confirm how the automated process went in final Handover meeting...

Donna confirmed she's happy with the schedule, and they're also already up to date with the final content.

May 2022:

  • Donna ran new report that Rick created to double check no invalid mappings, all clean now
  • Mark/Donna to complete mapping on Sunday/Monday (as drip feed failed last night so they won't get final content until Saturday...)
5Brief 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


6DevOps resource confirmedJoe will be the resource for the May release...
7Versioning and Change Freeze

Plan is to follow the new processes as now defined: 

AAT to sign off PreProduction (unversioned) build before 10:00 on 17th May, and then:

  • Versioning + related issues to be completed and resolved as of  - DONE!
8Stats Report

Reports run via the reporting platform:

9Risks
  1. Timing of AAT being away from 26th May - 14th June 
  2. First run through of the Mapping process automation 
10AOB