2023-01-11 ERM Weekly Delivery Update

Owned by Jag Goraya
Last updated: Jan 12, 2023
2 min read

Meeting Details

Date
 
Time

8:05am ET, 12:05pm UK, 1:05pm Germany

Location

Video Call in

Previously2022-12-14 ERM Weekly Delivery Update
ReferencesJIRA Issue Board

Goals

Participants

Apologies

  • Gill

Discussion items

Time

Item

Notes

<5 minsIntroductions

Call Priorities
  • ERM-2482 - Getting issue details... STATUS
  • ERM-2551 - Getting issue details... STATUS / ERM-2553 - Getting issue details... STATUS / ERM-2552 - Getting issue details... STATUS
    • to discuss with Zak

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-2537 - Getting issue details... STATUS
    • ERM-2557 - Getting issue details... STATUS
    • ERM-2558 - Getting issue details... STATUS
    • Progress / Impediments: 
      • reviewed
      • everything looks fine (with BigTest accommodated for plugins)
    • TODO: 
      • additional testing with agreements plugin
      • linting check
      • comment any changes
    • New unknowns: NA
    • Help or input needed: NA
    • ETA for review: ready to close
  • ERM-2482 - Getting issue details... STATUS
    • Progress / Impediments: 
      • issue scenario resolved and manually tested
      • written a unit test to address TI and PTI collation during PCI ingest
      • this revealed an underlying iterator bug
    • TODO: run some more tests 
    • New unknowns: NA
    • Help or input needed: 
      • Separately: any other coverage use cases to test before QA
    • ETA for review: today
  • ERM-2485 - Getting issue details... STATUS
    • Progress / Impediments: none yet
  • ERM-2525 - Getting issue details... STATUS
    • Progress / Impediments: 
    • TODO: 
    • New unknowns: 
    • Help or input needed: 
    • ETA for review: 

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

  • NA

Needs Elaboration

  • NA

Sprint Backlog - Next Up


Allocations

Claudia: NA

  • Ethan: 
  • Monireh:  RTL Completion

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

  • NA

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: Morning Glory R2022.2 Hotfix

Stories / Bugs

Previously

RTL / Tasks

  • NA

Release Tasks

Closed: Orchid R2023.1

Stories / Bugs

  • NA

RTL / Tasks

Closed (No ERM Release)

  • <10 mins

AOB


New Issues

Added to sprint

Not added to sprint

  • NA

Other

  • OS to look at getting Localize access to review status of translations. 

Component Updates

Release Planning

Testing