/
2022-08-10 ERM Weekly Delivery Update

2022-08-10 ERM Weekly Delivery Update

Aug 10, 2022

Meeting Details

Date

Aug 10, 2022 

Time

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

Location

Video Call in

Previously

2022-08-03 ERM Weekly Delivery Update

References

JIRA Issue Board

Goals

Participants

  • @Jag Goraya 

  • @Ethan Freestone 

  • @Owen Stephens 

  • @Peter Böhm 

  • @Gill Osguthorpe 

Apologies

  • Claudia Malzer

  • Monireh Rasouli

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

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

    • Progress / Impediments:

      • Tests written for components

    • TODO: 

      • Fix POLine filter

      • Implement review changes (such as agreementLines url)

    • New unknowns: NA

    • Help or input needed: NA

    • ETA for review: Fri/Mon

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

    • Progress / Impediments: 

      • vagrant box issues (resolved)

      • more fields being updated now

      • no new service required

    • TODO: 

      • many-to-many fields not working (alt resource name, content type) 

        • looks right,

        • need to debug each package line

      • Test Kbart, GOkb Import

    • New unknowns: NA

    • Help or input needed:

      • GOkb account

      • confirmed also to update `alternateResourceNames`

    • ETA for review:  Thursday

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

    • Progress / Impediments: 

      • just started to write up domain class

    • TODO: all of it

    • New unknowns: 

      • migrations expecting to be quite tricky

    • Help or input needed: NA

    • ETA for review: Sprint 147

 

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

Needs Elaboration

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:

  • NA

QA / UAT 

Bugfix Cycle 

 

 

Release Candidates

  • What has passed QA since last dev call?

  • What has been closed since last dev call?

Accepted

  • NA

Closed: Morning Glory R2022.2

Stories / Bugs

Closed: Morning Glory Big Fix R2022.2

Stories / Bugs

  • NA

Releases

  • NA

Closed: Nolana R2022.3

Stories / Bugs

RTL / Tasks

Closed (No ERM Release)

  • NA

  • <10 mins

AOB

 

New Issues

Added to sprint

Not added to sprint

  • NA

Other

  • Re ERM-2289

    • Button grouping to be reviewed at next SIG 10 Aug

      • changes expected

      • boiled down to two options

        1. collapsing tab group (would require new component)

        2. new (parent) tab group 

      • group has until Monday to review

    • Gill to raise new issue once confirmed