Child pages
  • 2020-10-07 ERM Weekly Delivery Update
Skip to end of metadata
Go to start of metadata

Meeting Details

Date 
Time

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

LocationVideo Call in FOLIO Slack: #erm-developers

Goals

Apologies

Discussion items

Previously: 2020-09-30 ERM Weekly Delivery Update


Time

Item

Notes

Action Items

<5 minsIntroductions



WIP Update

Release Candidates

For Release

Code Review: 

  • NA

QA / UAT 

  • ERM-1158 - Getting issue details... STATUS
  • ERM-1161 - Getting issue details... STATUS
  • ERM-1147 - Getting issue details... STATUS
  • ERM-1121 - Getting issue details... STATUS
    • Returned to Code Review to incorporate additional change for agreement lines.
    • Waiting for Jenkins build issue to be resolved - long queue of tasks from other repositories to process before PR is reviewable
  • ERM-633 - Getting issue details... STATUS
  • ERM-1140 - Getting issue details... STATUS
  • ERM-1142 - Getting issue details... STATUS
  • ERM-1163 - Getting issue details... STATUS

Items at Risk / Spillover

In Progress

  • ERM-1160 - Getting issue details... STATUS
    • Waiting for Jenkins build issue to be resolved - long queue of tasks from other repositories to process before this can be QAd

Sprint Backlog

  • ERM-1154 - Getting issue details... STATUS
    • the agreement name is being changed as if by poltergeists, because according to Grails 4 this shouldn't be happening. 
    • Ethan to investigate whether we are using any special logic
    • May need to hand to Steve
  • ERM-1159 - Getting issue details... STATUS
    • Adi to investigate
  • ERM-1116 - Getting issue details... STATUS
    • not started yet
  • ERM-1146 - Getting issue details... STATUS
    • to be picked up by Claudia
    • message banner should be persistent. as per standard component behaviour
    • similar in local-kb-admin
  • ERM-1152 - Getting issue details... STATUS
    • logging levels are intentionally set
    • Closing issue as Won't Fix as logging levels 
    • Separately
    • May be related to logback.groovy file setting for development environments
  • ERM-972 - Getting issue details... STATUS
    • a fix (for this and 1079) would be to make all permissions defined at a granular level
    • Not tricky, just time-consuming
    • OS advised to hold off on this for now
    • Reverted to reporter for clarification on why it is needed
    • Removed from sprint.
  • ERM-1156 - Getting issue details... STATUS

Blocked

  • NA

Needs Elaboration

  • ERM-1102 - Getting issue details... STATUS
    • ERM-1155 Ethan to write up handlebars approach
    • To feed into re-writes and redesigns of ERM-1048, ERM-1107, ERM-1109
      • expect to still show users example URLs

<10 minsAOB

Release Tasks

  • Issues ERM-1165 to ERM-1174 added 
  • JG to assign.

ERM-1079 - Getting issue details... STATUS

  • may be solved by ERM-972 if granular permissions are defined
  • not a priority to fix for Honeysuckle