/
2022-09-28 ERM Weekly Delivery Update

2022-09-28 ERM Weekly Delivery Update

Sep 28, 2022

Meeting Details

Date

Sep 28, 2022 

Time

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

Location

Video Call in

Previously

2022-09-21 ERM Weekly Delivery Update

References

JIRA Issue Board

Goals

Participants

  • @Jag Goraya 

  • @Monireh Rasouli 

  • @Gill Osguthorpe 

  • @Peter Böhm 

  • @Ethan Freestone 

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

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

    • Progress / Impediments: 

      • Comparing plugin and licenses/agreements

    • TODO: 

      • make change from org to orgs

    • New unknowns: 

      • Filters could be changed from orgs to org or vice versa:

        • should this matter? No

        • it just needs to be consistent

      • Minimal change is to update plugin from org to orgs

    • Help or input needed:

      • How to test it?

        • Add license to agreement and lookup license

        • Check Console > Header > Request URL

    • ETA for review:  today

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

    • Progress / Impediments: developed

    • TODO: testing

    • New unknowns / Help or input needed: 

      • record metadata gokb 

    • ETA for review: ready for QA tomorrow afternoon

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

    • Progress / Impediments:

      • should be done

      • tested locally

    • TODO: none

    • New unknowns / Help or input needed: 

    • ETA for review: PR today

 

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

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

    • relatively low priority against other UX issues

    • To note:

      • reduce font-size to match other parts of pane

      • wrap line before wrapping labels

      • maybe have spaces rather than columns? 

    • lots of css wrangling

      • size: derived from checkbox

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

Removed

 

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 

Bugfix Cycle 

  • NA

 

 

Release Candidates

  • What has passed QA since last dev call?

  • What has been closed since last dev call?

For Release / Pending Testrails

Closed: Nolana R2022.3

Stories / Bugs

RTL / Tasks

  • NA

Previously

Closed (No ERM Release)

  • NA

  • <10 mins

AOB

 

New Issues

Added to sprint

Not added to sprint

Other

Component Updates

  • SKC is at 3.0.1

Release Planning

  • No module release expected for Nolana for 

    • ui-handler-stripes-registry

    • mod-licenses