/
2019-11-27 ERM Weekly Delivery Update

2019-11-27 ERM Weekly Delivery Update

Owned by Jag Goraya
Last updated: Jan 15, 2020

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
  • Attendees / Apologies
  • Upcoming Availability
    • Only Peter and Steve available for dev on Thursday for rest of this sprint. 
    • Impact for QA bugs?
  •  
20 minsSprint Cutoff

  • Release Candidates

    • Code Review

      • ERM-558 - Getting issue details... STATUS
        • some minor tweaks but expected today

    • QA / UAT 

      • ERM-561 - Getting issue details... STATUS
      • ERM-459 - Getting issue details... STATUS
        • Previously: testing being done by Owen, Felix and Gill; some adjustments to fall out.
        • Owen Stephens Are the fallouts all (separately) logged now?  
      • ERM-578 - Getting issue details... STATUS
      • ERM-493 - Getting issue details... STATUS
      • ERM-418 - Getting issue details... STATUS
      • ERM-356 - Getting issue details... STATUS  / 
      • ERM-361 - Getting issue details... STATUS
      • ERM-579 - Getting issue details... STATUS
      • ERM-297 - Getting issue details... STATUS
      • ERM-376 - Getting issue details... STATUS
  • Items at Risk / Spillover
    • Open / Sprint Backlog
      • ERM-518 - Getting issue details... STATUS

    • In Progress

      • ERM-567 - Getting issue details... STATUS
        • Requires some input from Steve
      • ERM-463 - Getting issue details... STATUS
        • Nightmare tests being written
      • ERM-584 - Getting issue details... STATUS
        • Nightmare tests being written
  • Owen StephensERM-463 and ERM-584 are currently developed, but are in progress for writing nightmare tests. Do you want to wait til tests are complete or happy to release to Edelweiss with incomplete tests?

15 mins

New Issues

Brought into sprint: (related to  ERM-459 - Getting issue details... STATUS )

  • ERM-568 - Getting issue details... STATUS
  • ERM-587 - Getting issue details... STATUS

New and to be reviewed for progress: 

  • ERM-587 - Getting issue details... STATUS
  • ERM-588 - Getting issue details... STATUS
  • ERM-591 - Getting issue details... STATUS
  • ERM-592 - Getting issue details... STATUS
  • ERM-593 - Getting issue details... STATUS
  • ERM-594 - Getting issue details... STATUS
  • ERM-595 - Getting issue details... STATUS
  • ERM-596 - Getting issue details... STATUS
  • ERM-597 - Getting issue details... STATUS
  • ERM-600 - Getting issue details... STATUS
  • ERM-601 - Getting issue details... STATUS
  • ERM-602 - Getting issue details... STATUS
  • ERM-603 - Getting issue details... STATUS
  • ERM-604 - Getting issue details... STATUS
  • ERM-605 - Getting issue details... STATUS
  • ERM-606 - Getting issue details... STATUS
  • ERM-607 - Getting issue details... STATUS

10 mins

Next Sprint
  • TBC

<10 minsAOB
steve.osguthorpe  to follow up with Marc Johnson on translation strategy (following ERM-436). From last week: 

Any further thinking happened? 

  • Expecting to disallow not support editable lists for now


Related content