/
2022-11-30 ERM Weekly Delivery Update

2022-11-30 ERM Weekly Delivery Update

Nov 30, 2022

Meeting Details

Date

Nov 30, 2022 

Time

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

Location

Video Call in

Previously

2022-11-23 ERM Weekly Delivery Update

References

JIRA Issue Board

Goals

Participants

  • @Jag Goraya

  • @Monireh Rasouli 

  • @Gill Osguthorpe 

  • @Ethan Freestone 

  • @Claudia Malzer 

  • @Owen Stephens 

  • @Peter Böhm 

Apologies

 

Discussion items

Time

Item

Notes

Time

Item

Notes

<5 mins

Introductions

 

Call Priorities

https://folio-org.atlassian.net/browse/ERM-2470

  • still no clarification response from Reporter

Release Concerns:

Blocking Releases: 

 

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

Needs Elaboration

  • NA

Sprint Backlog - Next Up

https://folio-org.atlassian.net/browse/ERM-2480

  • Steve O working on this

  • Tenant bug resolved

    • Context: string templating going across tenants

  • Memory leak is still extant

    • happens when concurrent

  • Turning off string templating background task:

    • not clear that federated locking is definitely related, so removing this may not make a difference

    • would unblock ERM-2475 for QA

    • but could give a false impression of current status

  • Followuṗ contingency call scheduled for Thu 1 Dec 10am

https://folio-org.atlassian.net/browse/ERM-2452

https://folio-org.atlassian.net/browse/ERM-2468

https://folio-org.atlassian.net/browse/UXPROD-3904

https://folio-org.atlassian.net/browse/ERM-2481

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

  • NA

Sprint Backlog -  At Risk

Removed

 

 

 

 

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 (Nolana)

 

 

Release Candidates

  • What has passed QA since last dev call?

  • What has been closed since last dev call?

For Release / Pending Testrails

Closed: Morning Glory R2022.2 Hotfix

Stories / Bugs

RTL / Tasks

  • NA

Release Tasks

Closed: Nolana R2022.3 Bugfix

Stories / Bugs

RTL / Tasks

  • NA

Release Tasks

  • NA

Previously

  • NA

Closed: Orchid R2023.1

Stories / Bugs

  • NA

RTL / Tasks

Closed (No ERM Release)

  • NA

  • <10 mins

AOB

 

New Issues

Added to sprint

Not added to sprint

Other

Component Updates

  • Filter by electronics in Title Controller 

  • Regression from ERM-1850 / ERM-2443: Add Availability Scope

  • TO NOTE RE: Jobrunner and Federated Threads: 

    • whenever either is changed should test both string templating and federated tick and how they interact.

Release Planning

Testing

  • NA