/
2023-01-25 ERM Weekly Delivery Update

2023-01-25 ERM Weekly Delivery Update

Feb 20, 2023

Meeting Details

Date

Jan 25, 2023 

Time

11:30am UK, 12:30pm Germany

Location

Video Call in

Previously

2023-01-11 ERM Weekly Delivery Update

References

JIRA Issue Board

Goals

Participants

  • @Jag Goraya

  • @Monireh Rasouli 

  • @Ethan Freestone 

  • @Claudia Malzer 

  • @Owen Stephens 

Apologies

Discussion items

Time

Item

Notes

Time

Item

Notes

<5 mins

Introductions

 

Call Priorities

  • Add test to stripes-kint-components to check encoding of special characters

  • https://folio-org.atlassian.net/browse/STRIPES-834

    • ERM-2613 to ERM-2618

    • EF to review with ZB

    • Stripes have merged work without input from the team. 

  • Backend on Linux - expected to be up and running end of today

  • Jira down - issue specifics not available.

 

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-2611 / https://folio-org.atlassian.net/browse/ERM-2610

    • Progress / Impediments: 

      • Some issues to find the example PR 555

      • ERM-2610 in QA

      • Moved onto ERM-2611

    • Help or input needed:

      • Is the primary slug the Gokb UUID?

        • Not currently, but will be going forward. 

        • Therefore it appears twice in item header

      • Alternate slugs should be an array with >1 entry. 

        • This is for future proofing, and should be tested

        • But for Gokb, they will only have one.

      • Should package_shortcode in GOKbdAIAdaptor.groovy log entry routine be removed? 

        • Yes, an replace with gokb_uuid check instead. Package_shortcode is used when no reference is used. Removing it means we expect and have to assume a new package.

    • ETA for review: Wed 25 Jan(?)

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

    • Progress / Impediments: 

    • TODO: 

    • New unknowns: 

    • Help or input needed: 

      • Does this need backporting for Nolana or Morning Glory?

    • ETA for review: 

 

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

Needs Elaboration / Triage

Sprint Backlog - Next Up

 

Allocations

  • Claudia: NA

  • Ethan: ERM-2514, backports

  • Monireh: Set up backend environment in Linux

 

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

  • NA

Sprint Backlog -  At Risk

Removed

  • 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 

 

Release Candidates

  • What has passed QA since last dev call?

  • What has been closed since last dev call?

For Release / Pending Testrails

Closed: Orchid R2023.1

Stories / Bugs

  • NA

RTL / Tasks

Closed (No ERM Release)

  • NA

  • <10 mins

AOB

 

New Issues

Added to sprint

  • NA

Not added to sprint

Other

Component Updates

  • internal contacts and organisations need to be moved away from stripes-connect

Release Planning

Testing

Security

  • flag possible vs confirmed dependency issues 

  • need to review internal handling process