2020-03-18 ERM Weekly Delivery Update

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

Release Candidates

  • Code Review: 

    • ERM-783 - Getting issue details... STATUS
      • ready for testing
  • QA / UAT: non-laser testing expected complete this week

Items at Risk / Spillover

  • In Progress
    • In Progress
      • ERM-681 - Getting issue details... STATUS
        • Peter Böhm on leave - back next week / sprint
        • rollover to Sprint 86
      • ERM-705 - Getting issue details... STATUS
        • made more complex and unclean by having to send both operator and value in same control
        • isNull maybe an available option to concatenate bank strings
      • ERM-735 - Getting issue details... STATUS
        • more complex than initially thought
        • still with Steve
        • front-end tests need to be written
      • ERM-763 - Getting issue details... STATUS
        • good progress initially - term buckets being created
        • having Windows character encoding issues linking to licenses
        • need to set up a linux environment to make progress
      • ERM-768 - Getting issue details... STATUS
        • nearly ready for code review 
    • Open / Sprint Backlog
      • ERM-778 - Getting issue details... STATUS
        • Owen Stephens to check on laser channel whether preferred available option in the interim is to either (1) omit the date or (2) convert to text 
        • Owen Stephens to elaborate
        • Ethan Freestone needs to consider how customProperties are handled (as part of ERM-763)
        • Also noted:
          • may block some existing LASER functionality
          • is potentially wider than laser though
          • likely to manifest as an incorrect date/zone
          • if implemented as date type, has potential implications for query builder
          • current inclination is to store as text
          • removed from Sprint 85 for future prioritisation
  •  

15 mins

New Issues

Raised: 

  • ERM-773 - Getting issue details... STATUS
    • no type associated with data, which is causing a catastrophic failure
    • this issue catches and skips the offending row
    • column is not mandatory, which may cause a related but separate issue

Brought into sprint: 

  • ERM-783 - Getting issue details... STATUS
  • ERM-772 - Getting issue details... STATUS
  • ERM-771 - Getting issue details... STATUS
  • ERM-770 - Getting issue details... STATUS
  • ERM-769 - Getting issue details... STATUS

10 mins

Next SprintGoldenrod priorities likely to be extending to basic functionality (deletion, duplication etc) rather than new functionality concepts.
<10 minsAOB
  •