2021-12-15 ERM Weekly Delivery Update

Owned by Jag Goraya
Last updated: Dec 15, 2021

Meeting Details

Date

 

Time

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

Location

Video Call in

Previously2021-12-08 ERM Weekly Delivery Update
ReferencesJIRA Issue Board

Goals

Participants

Apologies

Discussion items

Time

Item

Notes

<5 minsIntroductions

Call Priorities
  • ERM-1850 - Getting issue details... STATUS
    • Issues with the whole ingest still
      • Large increase in Oct/Nov, so cursor progress is slow
      • Attempted late cursor fix, but does not seem to be evaluated
    • Previous crashes due to memory misconfiguration are resolved
    • job status needs to be set back to null or idle, as it is getting stuck at in-process
    • Now ublocked on ingest
    • Separate issue to be posted to Slack for Owen to investigate: https://folio-project.slack.com/archives/CAYCU07SN/p1639579052215200
  • ERM-1953 - Getting issue details... STATUS
    • got values displayed as string rather than UUID
    • getting lost with setting up tests
      • 'TypeError: require.context is not a function' error
      • needs to make sure icon is test setup
    • TODO:

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

  • ERM-1762 - Getting issue details... STATUS
    • infinite loop behaviour with getting settings from stripes-components
    • will try similar to how if eResourcesEnabled setting is wrapped, as a separate component
    • Also TODO: tests
  • ERM-1850 - Getting issue details... STATUS
  • ERM-1953 - Getting issue details... STATUS

Pending

Blocked

  • Are the blocking conditions still relevant? 
  • What action is needed to unblock, and by whom?

Needs Elaboration

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

Sprint Backlog

  • Who is picking up what next?
  • When is next issue expected to start / complete?
  • Anything needed to start next issue (dependencies or clarifications)?

Blocked

  • ERM-1941 - Getting issue details... STATUS
    • effectively blocked by FOLIO-3362 - Getting issue details... STATUS

Needs Elaboration

  • NA

Sprint Backlog - Next Up

  • Claudia:
    • NA
  • Ethan:
    • ERM-1923 - Getting issue details... STATUS ,
      • had some pointers from Steve and Ian
      • need to rule out whether json source is good 
    • ERM-1920 - Getting issue details... STATUS
      • if not, there may be an issue too look at with how we handle the id/object in line with grails patterns (preferably to not serialise in this case)
  • 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


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 

Aim to clear sprint without anything to carry over the holiday period

Bugfix Cycle 

  • NA



Release Candidates

  • What has passed QA since last dev call?
  • What has been closed since last dev call?

Accepted

New

  • NA

Closed: Lotus R1 2022

Features

RTL / Other Tests

<10 mins

AOB


New Issues

Added to sprint

  • NA

Not added to sprint

  • NA

Other