/
2023-03-22 ERM Weekly Delivery Update

2023-03-22 ERM Weekly Delivery Update

Mar 22, 2023

Meeting Details

Date

Mar 22, 2023 

Time

11:30am UK, 12:30pm Germany

Location

Video Call in

Previously

2023-03-15 ERM Weekly Delivery Update

References

JIRA Issue Board

Goals

Participants

  • @Jag Goraya

  • @Gill Osguthorpe

  • @Monireh Rasouli

  • @Claudia Malzer

  • @Ethan Freestone

  • @Owen Stephens  

Apologies

Discussion items

Time

Item

Notes

Time

Item

Notes

<5 mins

Introductions

 

Call Priorities

  • SI-12

 

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

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

    • Progress / Impediments: 

      • pattern was not matching

      • clarified with PO

    • TODO: un-draft PR

    • New unknowns / Help or input needed: NA

    • ETA for review: ready to go

  • https://folio-org.atlassian.net/browse/SI-12

    • Progress / Impediments: 

      • PR raised

    • TODO: 

      • resolve github actions warning

      • remove slash in line 75

    • New unknowns / Help or input needed: 

    • ETA for review: today

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

    • Progress / Impediments: 

      • Discussed logging with Owen

      • Will follow logging for old process (so can be applied to both)

      • logging work pushing back refactoring

      • switch to decide whether harvest or pushKb is now in place, operating at service level

      • delayed by cypress calls

      • Developer workflow / reset environments (from Ian)

    • TODO: 

      • some questions to take to users

        • OS to discuss with GBV

        • Martina to set up call 

        • To take forward separate (out of scope) to ERM-2630

      • align new logging with existing jobs 

      • followed by title ingest refactoring

      • update ERM-2631 with summary from conversation notes

    • New unknowns: NA

    • Help or input needed: 

      • Developer workflow / reset environments (from Ian)

        • further discussion needed about how to implement

        • needed for ERM-2631

 

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 / Triage

  • NA

Sprint Backlog - Next Up

Allocations

 

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

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:

  • NA

QA / UAT 

 

Release Candidates

  • What has passed QA since last dev call?

  • What has been closed since last dev call?

For Release / Pending Testrails

Closed: Poppy R2023.2

Stories / Bugs

  • NA

Maintenance / Tasks

  • NA

Release Tasks

Closed: Orchid R2023.1 Bugfix

Release Tasks

  • NA

Closed (No ERM Release)

  • <10 mins

AOB

 

New Issues

Added to sprint

Not added to sprint

Other

Component Updates

  • NA

Release Planning

Testing

Security