Skip to end of banner
Go to start of banner

2020-11-11 ERM Weekly Delivery Update

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Current »

Meeting Details

Date

    

Time

10:30am ET, 3:30pm UK, 4:30pm Germany

LocationVideo Call in FOLIO Slack: #erm-developers

Goals

Participants

Apologies


Discussion items

Previously: 2020-10-14 ERM Weekly Delivery Update

Time

Item

Notes

Action Items

<5 minsIntroductions



WIP Update 

Release Candidates

Code Review: 

    • NA

QA / UAT 

No impediments

Items at Risk / Spillover

In Progress

    • ERM-1048 - Getting issue details... STATUS
      • now have an endpoint that the system can interrogate deltas and run a refresh on changes, and then action where differences exist
      • no endpoint for platforms to request a refresh
        • would that be necessary?
        • effectively a selective manual force that also avoids heavy database churn
        • not to progress at this point
      • Tests and Docs to be updated
      • Ian to code review, along with docs
      • Code Review expected by EOW
    • ERM-1184 - Getting issue details... STATUS
      • added display settings option for title instances
      • ui developed in line with frontend
      • just a few tests to write, 
      • PR expected today
    • ERM-1204 - Getting issue details... STATUS
      • some local environment issues with
        • users app / frontend
        • backend error message re departments
        • need to comment out the vagrant file version number in mod-agreements (config.vm_version)
        • as per Vagrant Setup for ERM
        • could also point to snapshot (though won't see backend changes)
    • ERM-1216 - Getting issue details... STATUS
      • infrastructure is set up in erm components
      • this will be the source for other erm ui modules
      • next task would be to write tasks to add tests for different ui modules
      • BigTest was for end-to-end, but RTL is exclusively unit test
      • Adi to link up to docs for developersd

Sprint Backlog

  • ERM-1047 - Getting issue details... STATUS
    • pending 1048
    • any adjustment needed here? yes, ui aspects to be elaborated
    • see also sub:1136

Needs Elaboration

  • ERM-1214 - Getting issue details... STATUS ERM-1215 - Getting issue details... STATUS
    • descoped
  • ERM-1136 - Getting issue details... STATUS
    • closed as duplicate of 1048

Closed

<10 minsAOB

New Issues

All ready for development



  • No labels