/
2022-05-04 ERM Weekly Delivery Update

2022-05-04 ERM Weekly Delivery Update

May 04, 2022

Meeting Details

Date

May 4, 2022 

Time

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

Location

Video Call in

Previously

2022-04-27 ERM Weekly Delivery Update

References

JIRA Issue Board

Goals

Participants

  • @Jag Goraya 

  • @Ethan Freestone 

  • @Monireh Rasouli 

  • @Peter Böhm 

  • @Gill Osguthorpe 

  • @Claudia Malzer 

  • @Owen Stephens 

Apologies

Discussion items

Time

Item

Notes

Time

Item

Notes

<5 mins

Introductions

 

Call Priorities

 

 

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

NA

  • ISSUE

    • Blocking conditions

    • Action needed

Needs Elaboration

NA

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

    • Who / When: Owen

      • Move ERM-286 to task defining UXPROD-3591

      • Preserve ERM-2046 for ERM-287, ERM-288 and ERM-289

      • Split other subtasks into separate stories for different related subtasks

    • ETA Ready for Dev: 

Sprint Backlog - Next Up

 

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

 

In Review

  • Any impediments to review or QA?

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

 

Code Review: 

Plan:

  1. Complete 3066

  2. Clear code review 

  3. Merge 2066

Issues:

QA / UAT 

Bugfix Cycle 

  • NA

 

 

Release Candidates

  • What has passed QA since last dev call?

  • What has been closed since last dev call?

Accepted

Closed: Morning Glory R2022.2

Features

RTL / Other Tests

Other 

Closed (No ERM Release)

<10 mins

AOB

 

New Issues

Added to sprint

Not added to sprint

Other

Deprecation

  • Add /* DEPRECATED */ note to top of component

  • Add console.warn

  • Add Jira issue to remove