Skip to end of metadata
Go to start of metadata

Meeting Details

Date

 

Time

9:15am ET, 2:15pm UK, 3:15pm Germany

Location

Video Call in

Previously2021-12-01 ERM Weekly Delivery Update
ReferencesJIRA Issue Board

Goals

Apologies

  • Gill

Discussion items

Time

Item

Notes

<5 minsIntroductions

Call Priorities
  • ERM-1850 - Getting issue details... STATUS
    • no PCI or PTI entries in database (expecting ~40k)
    • no errors in Local KB harvest/jobs
      • previously has taken hours longer than standard Gokb ingest
    • no vagrant config changes
    • looks like title ingest is succeeding (though stalled in process, so package ingest is failing)
    • TODO:
      • rebuild vagrant 
      • try small recordset for development: stop title ingest partially (restarting mod-agreements) and then package ingest will start automatically 
    • Ethan has shared stable pinned vagrant box details with Peter
  • ERM-1953 - Getting issue details... STATUS
    • volume of lines is unknown, so not got clear data to optimise
    • should follow pattern used by orders, which is to fetch up to 1000
    • TODO: 
      • add new fetch 
      • filter new fetch based on id
      • provision fallback (show UUID) in case of fetch fail
  • ERM-1938 - Getting issue details... STATUS
  • ERM-1931 - Getting issue details... STATUS
    • retrieval line without resource should be at the bottom of the list (because sorting by resource.name -> ref > UUID)
    • could be that null is ignored, rather than treated as a sortable value
    • issue is that how the sorting behaviour is unclear

WIP 

  • 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


Pending

Blocked

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

Needs Elaboration

  • 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

  • Claudia:
    • TBD
  • Ethan:
  • Monireh: 
  • Peter:  

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

  • 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 

Aim to clear sprint without anything to carry over the holiday period

  • ERM-1926 - Getting issue details... STATUS
  • ERM-1927 - Getting issue details... STATUS
    • TODO: Raise related stripes issue 
  • ERM-1931 - Getting issue details... STATUS
  • ERM-1932 - Getting issue details... STATUS
  • ERM-1900 - Getting issue details... STATUS
  • ERM-1882 - Getting issue details... STATUS
  • ERM-1883 - Getting issue details... STATUS
  • ERM-1884 - Getting issue details... STATUS
  • ERM-1912 - Getting issue details... STATUS
  • ERM-1921 - Getting issue details... STATUS
  • ERM-1948 - Getting issue details... STATUS

Bugfix Cycle 

  • NA



Release Candidates

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

Accepted

New

  • NA

Closed: Lotus R1 2022

Features

RTL / Other Tests

  • NA
<10 mins

AOB


New Issues

Added to sprint

  • NA

Not added to sprint

  • NA

Other

  • Aim to clear sprint without anything to carry over the holiday period