2019-09-18 ERM Weekly Delivery Update

Owned by Jag Goraya
Last updated: Oct 14, 2020
1 min read

Meeting Details

Date

 

Time

09:30am ET, 2:30pm UK, 3:30pm Germany

LocationVideo Call in FOLIO Slack: #erm-developers

Roadmap Priorities


Participants

Apologies

Discussion items

Time

Item

Notes

Action Items

<5 minsIntroductions
  •  
20 minsSprint Cutoff

  • Items at Risk / Spillover

    • Open / Sprint Backlog

      • ERM-356 - Getting issue details... STATUS  - to pick up after ERM-394

    • In Progress

      • ERM-428 - Getting issue details... STATUS  - to merge along with ERM-429
      • ERM-429 - Getting issue details... STATUS  - controlling license done, which can be 
        • TODO: tests need updating as rendering has changed
        • aim for ready for QA on Friday.
      • ERM-410 - Getting issue details... STATUS  - all subtasks are `In QA` - anything left to develop, or can the parent issue be sent for QA? (tick)
      • ERM-270 - Getting issue details... STATUS  - working solution in a PR needs refactoring, aim to complete today
      • ERM-394 - Getting issue details... STATUS  - expecting today
      • ERM-371 - Getting issue details... STATUS  - TODO: tests are breaking, need updating

  • Release Candidates

    • Code Review: none

    • QA / UAT

      • ERM-444 - Getting issue details... STATUS
      • ERM-419 - Getting issue details... STATUS
      • ERM-168 - Getting issue details... STATUS
      • ERM-430 - Getting issue details... STATUS
      • ERM-395 - Getting issue details... STATUS
      • ERM-392 - Getting issue details... STATUS
      • ERM-393 - Getting issue details... STATUS
      • ERM-260 - Getting issue details... STATUS

15 mins

New Issues
  • ERM-447 - Getting issue details... STATUS
  • ERM-448 - Getting issue details... STATUS
  • ERM-449 - Getting issue details... STATUS

  • ERM-450 - Getting issue details... STATUS  

    • may be related to a separate Docker memory handling issue.

    • Steve has been in touch with Ian Hardy. Appears that container can be assigned to more memory than it is possible to use.

    • no ERM application error. 
    • workaround is to restart container.

5 mins

Next Sprint

Leverage and surface into UI the existing active_from and active_to fields.

Copy and link existing agreements to new agreements (link of different type, eg, supercede or replace). Should support post-cancellation-access links going forward. 


<10 minsAOB
  • Documentation starter: 
    • can we start to use the kind of JSON outputs 

ERM/Licenses/Re:Share Tool Selection Rationale  

  • Translation / refdata: Owen to document base list