Nov 30, 2022 

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

Video Call in

• FOLIO Slack: #erm-developers

• Backup (Meet): https://meet.google.com/oei-okoc-eys

2022-11-23 ERM Weekly Delivery Update

JIRA Issue Board

<5 mins

Introductions

• Attendees / Apologies

• Upcoming Availability 

Call Priorities

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

• still no clarification response from Reporter

Release Concerns:

• ERM-2480

  • string templating ingest is consuming resources that are manifesting unresponsive and OOM symptoms

• ERM-2469

• ERM-2431

• ERM-2475

Blocking Releases: 

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

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

WIP 

• 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-2417

  • Progress / Impediments: 

    • Change made to remove results initially

  • TODO: 

    • Add message text

  • New unknowns / Help or input needed: NA

  • ETA for review: TODAY

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

  • Progress / Impediments: 

    • Looking for where file extension is set 

      • believed to be handled by browser

      • not handled by download.blob parameters

  • TODO: 

    • Verify whether specifying file extension in downloadBlob, per Slack example, is sufficient

  • New unknowns: NA

  • Help or input needed: NA

  • ETA for review: ?

Pending

• Are the blocking conditions still relevant? 

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

• 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

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

  • requires triage

  • unable to recreate due to bugfest environment

  • TODO: reduce count of e-resources needed from 100 to 25 for Nolana (ERM-2489)

    • won't fix the underlying issue, but may help ease problems

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

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

Needs Elaboration

• NA

Sprint Backlog - Next Up

ERM-2480: Refactor string template to improve performanceClosedPreview

• 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-2478

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

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

Allocations

• Claudia:

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

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

• Ethan: 

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

    • closed

• Monireh:  ?

• Peter:  ?

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 

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

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

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

Bugfix Cycle (Nolana)

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

Release Candidates

• What has passed QA since last dev call?

• What has been closed since last dev call?

For Release / Pending Testrails

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

  • Needs to be pushed to Bugfest 

  • Delayed to avoid clash with ERM-2431

Closed: Morning Glory R2022.2 Hotfix

Stories / Bugs

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

  • dependency release only (no ERM module release)

  • requires rebuild of environment

RTL / Tasks

• NA

Release Tasks

Closed: Nolana R2022.3 Bugfix

Stories / Bugs

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

RTL / Tasks

• NA

Release Tasks

• NA

Previously

• NA

Closed: Orchid R2023.1

Stories / Bugs

• NA

RTL / Tasks

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

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

Closed (No ERM Release)

• NA

• <10 mins

AOB

New Issues

Added to sprint

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

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

Not added to sprint

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

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

• ERM-2480: Refactor string template to improve performanceClosedPreview currently blocking mod-agreements 5.3.x and 5.4.x release 

Testing

• NA