/
2021-10-06 ERM Weekly Delivery Update

2021-10-06 ERM Weekly Delivery Update

Oct 06, 2021

Meeting Details

Date

Oct 6, 2021 

Time

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

Location

Video Call in

Previously

2021-09-29 ERM Weekly Delivery Update

References

JIRA Issue Board

Goals

Participants

  • @Jag Goraya

  • @Monireh Rasouli

  • @Owen Stephens 

  • @Peter Böhm

  • @Aditya matukumalli

  • @Claudia Malzer

  • @Ethan Freestone

  • @Gill Osguthorpe

Apologies

NA

Discussion items

Time

Item

Notes

Time

Item

Notes

<5 mins

Introductions

 

Previous Actions

NA

 

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 

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

    • original issue no longer there

    • however, German translation cannot be checked until Localize updates translations 

      • currently appears (falls back?) in English on snapshot

      • may get better info on testing environment

    • TODO: request Localize refresh from Peter Murray

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

    • Q: should changes be reflected in dashboard? A: not currently

    • there is an issue with showing phone/email in Dashboard, which suggests the behaviour needs to be overwritten

      • there is a separate card in Dashboard that overwrites the stripes-erm-components view

      • this difference is accepted 

    • good to proceed to For Release,

    • TODO: testrails review by Owen

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

    • returned to dev

    • changing integration tests has resulted in minor tweaks that will require testing

      • these have passed now, which satisfies remaining code review requirements

    • TODO: 

      • push to QA

      • rerun QA

      • test with switch for idFirst and titleFirst matching

Bugfix Cycle 

  • NA

 

 

WIP 

  • What progress or impediment on previously stated actions?

  • What's left to do?

  • What help or input is needed?

  • When expected to be ready for review?

In Progress

 

Pending

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

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?

Blocked

  • Are the blocking conditions still relevant? 

  • What action is needed to unblock, and by whom?

Sprint Backlog - Next Up

  • Claudia: 

    • PackageCardExternal:

      • pointers at existing card tests

      • nothing special 

      • mostly just key values

  • Peter:  Incorporate ERM-1879 into ERM-1813

  • Ethan: review Sprint 125 options

  • Adi:

    • frontend releases

  • Monireh: RTL

Sprint Backlog - to follow

  • NA

Needs Elaboration

Blocked

  • NA

 

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 

 

Release Candidates

  • What has passed QA since last dev call?

  • What has been closed since last dev call?

Accepted 

  • NA

Closed

Released

<10 mins

AOB

 

New Issues

Added to sprint

Not added to sprint

Other