/
2023-05-17 ERM Weekly Delivery Update

2023-05-17 ERM Weekly Delivery Update

Owned by Jag Goraya
Last updated: May 17, 2023

Meeting Details

Date
 
Time

11:30am UK, 12:30pm Germany

Location

Video Call in

Previously2023-05-03 ERM Weekly Delivery Update
ReferencesJIRA Issue Board

Goals

Participants

Apologies

Discussion items

Time

Item

Notes

<5 minsIntroductions

Call Priorities

ERM-2924 - Getting issue details... STATUS

  • side effect of not setting app setting appropriately., as permitted by ERM-2921
  • Owen to check with Julian what the expected behaviour is
  • could potentially add nullish check as a fallback (or some other exception handling)

ERM-2646 - Getting issue details... STATUS

  • removed direct dependency, so should no longer be an issue

ERM-2903 - Getting issue details... STATUS

  • Add Empty option and supporting behaviour

WIP 

 In Progress
  • ISSUE: 
    • Progress / Impediments: 
    • TODO: 
    • New unknowns: 
    • Help or input needed: 
    • ETA for review: 
  • What progress or impediment on previously stated actions?
  • What's left to do?
  • Any new unknowns?
  • What help or input is needed?
  • When expected to be ready for review?

In Progress

  • ERM-2641 - Getting issue details... STATUS
    • Progress / Impediments: 
      • first attempt to release by Steve this morning
      • blocked by maven
      • otherwise clear to proceed
    • TODO: 
      • Release by Steve (plugins)
      • Release by Ethan (back-end modules)
    • New unknowns: NA
    • Help or input needed: 
      • update needed for documentation? confer with Steve
    • ETA for review: this week
  • ERM-2421 - Getting issue details... STATUS
    • TODO:
      • Basket changes required
      • Will break ERM-2773 once that is merged
    • ETA for review: today
  • ERM-2909 - Getting issue details... STATUS
    • Progress / Impediments
      • matchkey title limited and not handled
      • no try catch around this causing those not to be ingested
      • standardised truncation to a stringUtils method
    • TODO: 
      • apply truncate fix
    • New Unknowns:
      • Set matchkey to infinite length? (instead of changing title length) NO 
      • Or truncate and lose data? YES
        • may result in future remedial work
    • ETA for review: tomorrow

Pending

 Blocked
  • ISSUE
    • Blocking conditions
    • Action needed
  • Are the blocking conditions still relevant? 
  • What action is needed to unblock, and by whom?


 Needs Elaboration
  • ISSUE: 
    • Who / When: 
    • ETA Ready for Dev: 
  • Who needs to be involved in the elaboration process? 
  • What is the timeframe for getting input?
  • When is the issue expected to be ready for development?


 Sprint Backlog


  • Who is picking up what next?
  • When is next issue expected to start / complete?
  • Anything needed to start next issue (dependencies or clarifications)?

Blocked

  • ERM-2918 - Getting issue details... STATUS
    • Ethan to progress with adding limit

Needs Elaboration / Triage

  • NA

Sprint Backlog - Next Up

  • NA

Allocations

  • Claudia: 
  • Ethan: 
  • Jack: NA

At Risk

  • What is now at risk of not being started this sprint?
  • Do any of these take priority over other sprint backlog items?

Sprint Backlog - to follow

Sprint Backlog -  At Risk

Removed

  • NA

In Review

  • Any impediments to review or QA?
  • Any useful context, implementation choices or limitations for the reviewer/tester to know ?


Code Review:

QA / UAT 


Release Candidates

  • What has passed QA since last dev call?
  • What has been closed since last dev call?

For Release 

Pending Testrails

  • NA


Closed: Nolana Hot Fix


Closed: Poppy R2023.2

Stories / Bugs

Maintenance / Tasks

  • NA

Release Tasks

Closed (No ERM Release)

  • <10 mins

AOB


New Issues

Added to sprint

  • NA

Not added to sprint

  • NA

Other

  • NA

Component Updates

  • NA

Release Planning

Testing

Security

Related content