/
2022-05-18 ERM Weekly Delivery Update

2022-05-18 ERM Weekly Delivery Update

May 23, 2022

Meeting Details

Date

 

Time

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

Location

Video Call in

Previously2022-05-11 ERM Weekly Delivery Update
ReferencesJIRA Issue Board

Goals

Participants

Apologies

  • Peter Bohm

Discussion items

Time

Item

Notes

<5 minsIntroductions

Call Priorities

WIP 

 In Progress
  • 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

  • ERM-2059 - Getting issue details... STATUS
  • ERM-2081 - Getting issue details... STATUS
    • Progress / Impediments: 
      • error doesn't materialise consistently for dev
      • outputs are as expected
      • getComponentsFromType is passed widgetType and used by useWidgetDefinition
      • tracing rendering back, there is no loading in useWidgetDefinition
    • TODO: 
      • add loading check to getComponentsFromType (returning Spinner)
      • remove it from simpleSearch
      • make sure there is always a returned value
    • New unknowns: NA
    • Help or input needed: NA
    • ETA for review: 
  • ERM-2124 - Getting issue details... STATUS  
    • Progress / Impediments: 
      • modelling in toolkit done
      • tests complete
    • TODO: 
      • double-check bindings 
      • check and set up for migrations
      • release web-toolkit-ce (Steve)
    • New unknowns: none
    • Help or input needed: none
    • ETA for review: Thu 
  • https://folio-org.atlassian.net/browse/ERM-1326
    • to set as deprecated

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


Pending

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


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


 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

NA

  • ISSUE
    • Blocking conditions
    • Action needed

Needs Elaboration

NA

Sprint Backlog - Next Up

ERM-2157 - Getting issue details... STATUS

ERM-2121 - Getting issue details... STATUS

ERM-2156 - Getting issue details... STATUS




In Review

  • Any impediments to review or QA?
  • Any useful context, implementation choices or limitations for the reviewer/tester to know ?


Code Review: 

QA / UAT 

  • ERM-2060 - Getting issue details... STATUS / ERM-2076 - Getting issue details... STATUS / ERM-2046 - Getting issue details... STATUS
    • Waiting on ERM-2045 and ERM-2059
  • ERM-1986 - Getting issue details... STATUS
  • ERM-1850 - Getting issue details... STATUS
  • ERM-2079 - Getting issue details... STATUS
  • ERM-2066 - Getting issue details... STATUS
  • ERM-2085 - Getting issue details... STATUS

Bugfix Cycle 

Carried Forward



Release Candidates

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

Accepted

Carried Forward

Closed: Lotus Hot Fix #1

NA

Closed: Morning Glory R2022.2

Features

  • NA

RTL / Other Tests

Other / Spring4Shell

Closed (No ERM Release)

  • <10 mins

AOB


New Issues

STRIPES-675

  • key summary components status
    Refresh

Added to sprint

  • ERM-2156 - Getting issue details... STATUS / ERM-2155 - Getting issue details... STATUS  
  • ERM-2172 - Getting issue details... STATUS
    • continuation of ERM-2059

Not added to sprint

Other