Jun 7, 2023 

11:30am UK, 12:30pm Germany

Video Call in

• FOLIO Slack: #erm-developers

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

2023-05-24 ERM Weekly Delivery Update

JIRA Issue Board

<5 mins

Introductions

• Attendees / Apologies

• Upcoming Availability 

Call Priorities

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

  • Progress / Impediments: 

    • Release by Steve (plugins)

    • ready to merge ERM modules

  • TODO: 

    • Release back-end modules

  • New unknowns: NA

  • Help or input needed: 

    • update needed for documentation? confer with Steve

  • ETA for review: today

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

  • Progress/Impediments:

    • every time to delete / add new coverage, a multiplying loop is happening at the backend

    • moving the saves around isn't making a difference

    • cross-checking coverage calculation in title instance to suppress update isn't making a difference

  • TODO:

    • check coverage list equality in setCoverageFromSchema

    • if equal, don't save

    • QA using files adapted from ERM-850

  • ETA for review: next week

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

• NA

Needs Elaboration / Triage

• NA

Sprint Backlog - Next Up

• NA

Allocations

• Claudia: 

  • NA

• Ethan: 

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

• Jack: 

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

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

• NA

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:

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

  • one or two tests failing due to local environment

  • Jack and Ethan reviewing to resolve local test issue

QA / UAT 

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

  • resolved. moving to closed. 

Release Candidates

• What has passed QA since last dev call?

• What has been closed since last dev call?

For Release / Awaiting Deployment

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

  • is actually on master for Poppy

  • resolved for Orchid (ERM-2933)

  • awaiting Nolana (ERM-2932) environments rebuild for testing 

Pending Testrails

• NA

Closed: Nolana CSP

• NA

Closed: Orchid CSP

• NA

Closed: Poppy R2023.2

Stories / Bugs

• NA

Maintenance / Tasks

• NA

Release Tasks

Closed (No ERM Release)

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

  • Updated to 4.7.0

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

• <10 mins

AOB

New Issues

• NA

Added to sprint

• NA

Not added to sprint

• NA

Other

• NA

Component Updates

• SKC 4.7.0 has been released with a new ComboButton component

Release Planning

• Partial release candidates should be determined before adding Grails 5 upgrade 

Testing

Security