2020-01-08 ERM Weekly Delivery Update

Owned by Jag Goraya
Last updated: Jan 08, 2020
1 min read

Meeting Details

Date

 

Time

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

LocationVideo Call in FOLIO Slack: #erm-developers

Participants

Apologies

Discussion items

Time

Item

Notes

Action Items

<5 minsIntroductions


20 minsSprint Cutoff

  • Release Candidates

    • Code Review - NA

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

    • QA / UAT

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

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

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

  • Items at Risk / Spillover
    • Open / Sprint Backlog - NA
    • In Progress
      • ERM-591 - Getting issue details... STATUS  - expected ready for QA Thu
      • ERM-454 - Getting issue details... STATUS  - issues exposing the right object(?)
      • ERM-644 - Getting issue details... STATUS
  •  

15 mins

New Issues

Raised

  • ERM-645 - Getting issue details... STATUS  /  ERM-646 - Getting issue details... STATUS
    • ERM-646 made subtask of ERM-645, as they will be done together
    • steve.osguthorpe to add summary of agreed approach to parent issue (something along the lines of using js:number and Java:BigInt, which should subsume other numeric requirements)
  • ERM-647 - Getting issue details... STATUS
    • backend to add weight as secondary sort
    • added to Ready to Progress
  • ERM-649 - Getting issue details... STATUS
    • what is the better message that's needed? - as per ERM-437
    • will be seen during concurrent editing
    • added to Ready to Progress - good quick fix
  • ERM-650 - Getting issue details... STATUS
    • to be prioritised against license deletion via UI

Brought into sprint: 

  • NA

10 mins

Next Sprint

TBC.  Early quarter focus expected to be around package / content comparison, which is valuable to support renewal decision-making.


<10 minsAOBNA
  •