/
2023-02-01 ERM Weekly Delivery Update

2023-02-01 ERM Weekly Delivery Update

Feb 20, 2023

Meeting Details

Date

Feb 1, 2023 

Time

11:30am UK, 12:30pm Germany

Location

Video Call in

Previously

2023-01-25 ERM Weekly Delivery Update

References

JIRA Issue Board

Goals

Participants

  • @Jag Goraya

  • @Monireh Rasouli 

  • @Owen Stephens 

  • @Ethan Freestone 

  • @Gill Osguthorpe 

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

 

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-2612

    • Progress / Impediments: 

      • backend work completed and merged (Claudia)

    • TODO: 

      • rename AgreementContentType to SubscriptionAgreement.contentType

      • update for package (allowed externally, is contentType.contentType, which should be pkg.contentType)

        • no impact on ingest service

        • update packagesRoute

      • frontend work to start later today

    • New unknowns: NA

    • Help or input needed: 

      • permissions issue on vagrant

        • workaround: need to add specific perm, run script again, re-log-in

      • drop tenant or re-run register/enable script to pick up migrations to see dropdown values

      • saving multivalue fields

        • no direct examples in this scenario

        • supplementary props would be an indirect example, but  is structurally different

    • 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: 

    • update contentType for SA and package

    • update packagesRoute

  • Ethan: 

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

      • concerns about leaving in stripes-testing, as we want to make them more active to support testrails level tests

      • interactors needed in stripes-erm-testing, which wouldn't be available in e2e tests

        • would need bleeding edge system

      • other teams already have written some e2e agreements tests, which we might need to be mindful of

      • propose to:

        • set up e2e in stripes-erm-testing

        • would mean we still test as part of our module/flower release process

        • key thing is to be able to reuse interactors and other erm testing library assets

  • Monireh: 

    • ERM-2612 frontend

 

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

  • 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

RTL / Tasks

  • NA

Closed (No ERM Release)

  • <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

JG to add e2e stub issue

Security

  • NA