Skip to end of banner
Go to start of banner

2019-11-13 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 2 Current »

Meeting Details

Date
 
Time

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

LocationVideo Call in FOLIO Slack: #erm-developers

Apologies

Discussion items

Time

Item

Notes

Action Items

<5 minsIntroductions
  •  
20 minsSprint Cutoff
  • Items at Risk / Spillover

    • Open / Sprint Backlog
      • ERM-376 - Getting issue details... STATUS
        • should be ready to test Friday
      • ERM-356 - Getting issue details... STATUS
        • should be ready to test Thursday
      • ERM-557 - Getting issue details... STATUS
      • ERM-558 - Getting issue details... STATUS
    • In Progress

      • ERM-393 - Getting issue details... STATUS
      • ERM-548 - Getting issue details... STATUS
        • Resolved as part of ERM-508
  • Release Candidates

    • Code Review:

      • ERM-459 - Getting issue details... STATUS
        • backend completed
        • some front-end issues to fix
        • expected to be ready to QA Thursday
      • ERM-436 - Getting issue details... STATUS
      • ERM-549 - Getting issue details... STATUS
    • QA / UAT: 

      • ERM-546 - Getting issue details... STATUS
        • Uncovered new bug (to be raised), that only the first harvesting from GOKb works - subsequent harvests do not execute.
        • RBSync status is not changed from In Progress. 
        • Import outcome logged as failure rather than partial. 
        • this issue will be ready to progress
      • ERM-515 - Getting issue details... STATUS
        • merged today - ready to QA Thu


15 mins

New Issues
  • ERM-553 - Getting issue details... STATUS
  • ERM-556 - Getting issue details... STATUS
  • ERM-557 - Getting issue details... STATUS
  • ERM-558 - Getting issue details... STATUS
  • ERM-560 - Getting issue details... STATUS
    • will hit the same kind of performance issues that were faced with package content
    • code is in place to handle this as described, but seems to have regressed
    • bringing into active sprint

10 mins

Next Sprint
  • ERM-518 - Getting issue details... STATUS
  • ERM-505 - Getting issue details... STATUS
  • ERM-538 - Getting issue details... STATUS
  • ERM-362 - Getting issue details... STATUS
  • ERM-297 - Getting issue details... STATUS

<10 minsAOB


  • No labels