/
2022-12-14 ERM Weekly Delivery Update

2022-12-14 ERM Weekly Delivery Update

Dec 14, 2022

Meeting Details

Date

Dec 14, 2022 

Time

10:05am ET, 2:05pm UK, 3:05pm Germany

Location

Video Call in

Previously

2022-12-07 ERM Weekly Delivery Update

References

JIRA Issue Board

Goals

Participants

  • @Jag Goraya

  • @Gill Osguthorpe 

  • @Owen Stephens 

  • @Peter Böhm 

  • @Claudia Malzer 

Apologies

  • Ethan

Discussion items

Time

Item

Notes

Time

Item

Notes

<5 mins

Introductions

 

Call Priorities

  • https://folio-org.atlassian.net/browse/ERM-2538

    • Fix needed in either stripes-kint-components (possibly) or stripes-erm-components (likely)

    • Need to

      • Backport a tiny addition to stripes-kint-components to v2 and v3 

      • Cherry pick changes to erm-components/ui-agreements/ui-licenses for MG/Nolana release branches.

  • https://folio-org.atlassian.net/browse/ERM-2482

    • Comment added to describe coverage logic

    • Overlaps and multiple coverage should exist

      • At what point does it check for the overlap?

      • What does it do next?

      • Why does it lead to a PCI not loading

    • Should not be asking if coverage overlap exists for separate PCIs, but same PCI

      • How does the system know that a subsequent PCI is repeated? 

        • Based on the PTI and Package

        • QUESTION: is this working correctly

    • QUESTION: is this happening because we're blocking upload of different , or because we are blocking two separate PCIs

 

WIP 

  • ISSUE: 

    • Progress / Impediments: 

    • TODO: 

    • New unknowns: 

    • Help or input needed: 

    • ETA for review: 

  • What progress or impediment on previously stated actions?

  • What's left to do?

  • Any new unknowns?

  • What help or input is needed?

  • When expected to be ready for review?

In Progress

 

Pending

  • ISSUE

    • Blocking conditions

    • Action needed

  • Are the blocking conditions still relevant? 

  • What action is needed to unblock, and by whom?

 

  • ISSUE: 

    • Who / When: 

    • ETA Ready for Dev: 

  • Who needs to be involved in the elaboration process? 

  • What is the timeframe for getting input?

  • When is the issue expected to be ready for development?

 

 

  • Who is picking up what next?

  • When is next issue expected to start / complete?

  • Anything needed to start next issue (dependencies or clarifications)?

Blocked

  • NA

Needs Elaboration

Sprint Backlog - Next Up

 

Allocations

Claudia: NA

 

At Risk

  • What is now at risk of not being started this sprint?

  • Do any of these take priority over other sprint backlog items?

Sprint Backlog - to follow

  • NA

Sprint Backlog -  At Risk

Removed

  • NA

 

In Review

  • Any impediments to review or QA?

  • Any useful context, implementation choices or limitations for the reviewer/tester to know ?

 

Code Review:

QA / UAT 

Bugfix Cycle (MG HF 1)

 

Release Candidates

  • What has passed QA since last dev call?

  • What has been closed since last dev call?

For Release / Pending Testrails

  • NA

Closed: Morning Glory R2022.2 Hotfix

Stories / Bugs

Previously

RTL / Tasks

  • NA

Release Tasks

  • NA

Closed: Orchid R2023.1

Stories / Bugs

  • NA

RTL / Tasks

  • NA

Closed (No ERM Release)

  • <10 mins

AOB

 

New Issues

Added to sprint

Not added to sprint

  • NA

Other

  • OS to look at getting Localize access to review status of translations. 

Component Updates

Release Planning

  • 22 Dec: Morning Glory Hotfix

Testing