Page tree

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Date of Initial Handover meeting: 13 April 2023

Date of Final Handover meeting: 18 April 2023

Attendees

Handover Status

INITIAL 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
  5. Content Team to confirm to Release Manager that 4x MRCM refset files are complete and ready to be released (they are then extracted from the termServer during release builds via the termServer Export)
2

Discussion of existing Known Issues from the previous Release

  1. Traceability issues for January 2023 release - NONE.
  2. Traceability issues for February 2023 release - https://jira.ihtsdotools.org/browse/FRI-576 2 failures both confirmed as false positives by Michael.
  3. Traceability March 2023 release - NONE on MAIN (2 failures found on project confirmed false positives not seen in daily build after promotion https://jira.ihtsdotools.org/browse/INFRA-10533)
  4. Traceability for April 2023 release - 8 failures on main checked and false positives, ticket is here INFRA-10712 - Getting issue details... STATUS


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 - failures for lateralizable reference set all false positives INFRA-10756 - Getting issue details... STATUS
  2. NEW and CHANGED MRCM report - no changes for April 2023 release confirmed with Yong https://docs.google.com/spreadsheets/d/1WgwjaSvYBDwPkrwW86gtYo3AnPuVS7D_lnByPXWFWZM/edit#gid=0
  3. Ref set description changes April 2023 release -none found in descriptions file https://docs.google.com/spreadsheets/d/1kO5zFJwtqfLYY1VgeZ3axEzOyARgz_R0AthwsaZVjvo/edit#gid=0


4Mapping schedule

January 2023:

  • ICD-0 - 1 new records + 0 inactivations expected
  • ICD-10 - expecting 550 ish changes (plus tonight's drip feed) due to large number of intentional inactivations this cycle
  • No expected issues this cycle...
    • Confirmed in final numbers!

February 2023:

  • ICD-0 - 1 new records + 0 inactivations expected
  • ICD-10 - expecting 500 ish changes (plus tonight's drip feed) due to large number of intentional inactivations this cycle
  • No expected issues this cycle...
    • Confirmed in final numbers!

March 2023:

  • ICD-0 - 2 new records + 0 inactivations expected
  • ICD-10 - expecting 315 ish changes (plus tonight's drip feed) due to large number of intentional inactivations this cycle
  • No expected issues this cycle...
    • Confirmed in final numbers!

April 2023:

  • ICD-0 - 6 new records + 2 inactivations expected
    • + for the specific fixes for this cycle we're expecting 7 records that should have been inactivated in March but were not, but should be now
    • + Rick is going to tweak the Mapping Dashboard to give Donna more visibility of the final expected map figures (EXCLUDING "no target" maps which she would normally include in her figures but which we wouldn't see coming out of the Delta files)
  • ICD-10 - expecting 537 ish changes (plus tonight's drip feed) due to large number of intentional inactivations this cycle
  • No expected issues this cycle...
    • Confirmed in final numbers!

***** NOTE:  Make sure that we keep an eye on the upgrade to ICD-0 version 3.2/3.4, as it "MAY" happen at some point in 2023 *****

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.


6DevOps resource confirmed
7Versioning 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??

HIGH LEVEL KEY MILESTONES:

  • 13/04/23 - All content and mapping complete and signed off by close of play
  • 18/04/23  - AAT to build PreProduction (unversioned) and sign off by the deadline, otherwise decision made to postpone versioning
  • 19/04/23 -  Versioning to begin first thing + related issues to be completed and resolved by 17:00
8Stats Report

Reports run via the reporting platform:

Summary Component stats for edition 13 April 2023:

https://docs.google.com/spreadsheets/d/1BK_xMk-U8UA22JVPmXM29f_wS_Adtdbc_veJHSjS0Hk/edit#gid=0


9Risks


10AOB

For information - there has been a P1 issue with validation in the authoring platform, this has meant that there have been no project promotions with content since 6 April 2023, the patch deployment was made today, details here FRI-641 - Getting issue details... STATUS  I had to promote a project this morning to fix a content issue and the validation ran without a problem, the daily build RVF report has also been run this morning and has completed, no issues (other than known issues) found.






  • No labels