/
2022-08-24 ERM Weekly Delivery Update

2022-08-24 ERM Weekly Delivery Update

Aug 24, 2022

Meeting Details

Date

Aug 24, 2022 

Time

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

Location

Video Call in

Previously

2022-08-17 ERM Weekly Delivery Update

References

JIRA Issue Board

Goals

Participants

  • @Jag Goraya 

  • @Ethan Freestone 

  • @Peter Böhm 

  • @Claudia Malzer 

Apologies

  • Owen Stephens

  • Monireh Rasouli

  • Gill Osguthorpe

Discussion items

Time

Item

Notes

Time

Item

Notes

<5 mins

Introductions

 

Call Priorities

 

 

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-2328

    • Progress / Impediments: NA

    • TODO: 

      • Not required

      • Closed

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

    • Progress / Impediments: 

      • domain class, migrations done

    • TODO: 

      • run tests 

    • New unknowns: NA

    • Help or input needed: NA

    • ETA for review: End of today

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

    • Progress / Impediments: 

    • TODO: 

      • iterate first over the current attributes to check if included in the first 

      • if not, remove each separately

      • iterate over new list being ingested, and check for attribute presence, and remove if not

      • complete as a single transaction (should already be in place, as saving at the end)

      • potentially add a compare list routine to reuse code (not expected)

    • New unknowns: NA

    • Help or input needed:

      • work out how to do it in Groovy with different data types

    • ETA for review: Thu/Mon

 

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

Needs Elaboration

Sprint Backlog - Next Up

 

 

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

 

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 

Bugfix Cycle 

  • NA

 

 

Release Candidates

  • What has passed QA since last dev call?

  • What has been closed since last dev call?

Accepted

  • NA

Closed: Nolana R2022.3

Stories / Bugs

  • NA

RTL / Tasks

Closed (No ERM Release)

  • <10 mins

AOB

 

New Issues

Added to sprint

  • NA

Not added to sprint

  • NA

Other

  • mod-service-interaction and ui-dashboard will need the breaking changes from ERM-2312 to work in development environments.

  • ui-agreements has breaking changes from ERM-2289

    • new example of a single component with two separate url routes to access

    • new changes check request origin to make sure that user is returned to the correct place afterwards

  • Vagrant box is deprecated