Meeting Details

Date

13 Dec 2023

Status

subtle	true
colour	Yellow
title	DRAFT

Time

11:30am UK, 12:30pm Germany

Location

Video Call in

FOLIO Slack: #erm-developers
Backup (Meet): https://meet.google.com/oei-okoc-eys

Previously

2023-11-15 ERM Weekly Delivery Update

References

JIRA Issue Board

Goals

ERM Sprint 180

Participants

Apologies

Discussion items

Time

Item

Notes

<5 mins

Introductions

Attendees / Apologies
Upcoming Availability
Calls:
- Last in 2023: 13 Dec
- First in 2024: 8 Jan → Sprint 182 Planning
- No Sprint 181

Call Priorities

Jira Legacy
server System JiraJIRA
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key RANCHER-1120
- Are the related FAT issues supposed to be Closed also?
Jira Legacy
server System JiraJIRA
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key SI-38
- grails-okapi release decision?
Jira Legacy
server System JiraJIRA
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key SI-34
/
Jira Legacy
server System JiraJIRA
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-3089
- release or wait? folowfollow-up to confirm go-ahead with Steve.

WIP

Expand

title	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

Jira Legacy
server System JiraJIRA
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-2631
- Progress / Impediments:
  - getting stuck on deployment
    - parked keycloak and auth
  - prototype logic for fetching and storing gokb queue of data
    - better insight into how queue management should happen to be faster and more resilient
      - newest backwards in each queue, rather than cursor forwards
      - if multiple changes made to source id, only see once
      - will mean new ingestors will have different data presented
  - learning curve for switching from declarative rather than imperative programming
- TODO NEXT:
  - add to queue and set pointer
  - force crash to test re-run
- TODO LATER
  - then transform saved json
  - then write algorithm to traverse queue with reactive streams
- AND
  - trying to write models for differing sources triggered on varying schedule
  - some kind of interface with(in) pushkb to set up (1) sources and (2) related implementations
  - add handling logic for interpreted source-implementation
- Help or input needed:
  - keycloak implementation (when deploying)
Jira Legacy
server System JiraJIRA
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-3089
- Progress / Impediments: blocked
- TODO: release
- Help or input needed: branch release of KIWT
Jira Legacy
server System JiraJIRA
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-2793
- Progress / Impediments:
  - MC changes
  - working on action button
- TODO:
  - proxies
  - new test for proxy server setting
- New unknowns / Help or input needed:
- ETA for review: Wednesday
Jira Legacy
server System JiraJIRA
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-3090
- Progress / Impediments:
  - udaed
  - assigned to Steve for QA
- TODO:
Jira Legacy
server System JiraJIRA
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-3063
- Progress / Impediments:
  - differences between what was pushed up and what was wanted
  - spotted by checks failing against number generator
  - missing value and owner
  - no picklist values being populated on backend
    - try with dropped tenant
    - may be related to local web toolkit changes?
- TODO:
  - resolve
  - once QA'd add comment with final set of migrations
  - needs testing
- New unknowns / help or input needed:
  - refdata has @default annotation, so db checks for and creates missing value which could get removed but ends up looking like it exists but in fact only an errant object with missing refdata exists
    - would need some kind of refdata cleanup, probably not via UI
- ETA for review: today
Jira Legacy
server System JiraJIRA
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-3124
- api mapping and requirement details added

Pending

Expand

title	Blocked

ISSUE
- Blocking conditions
- Action needed

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

Expand

title	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?

Expand

title	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 / Triage

NA

Sprint Backlog - Next Up

Jira Legacy
server System JiraJIRA
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-3122

Allocations

Claudia:
- NA
Ethan:
- Jira Legacy
  server System JiraJIRA
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key SI-38
Jack:
- Jira Legacy
  server System JiraJIRA
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key ERM-3078
Monireh:
- Jira Legacy
  server System JiraJIRA
  serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
  key ERM-2792

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

Release Tasks

Sprint Backlog - At Risk

Jira Legacy
server System JiraJIRA
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key SI-38

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:

Jira Legacy
server System JiraJIRA
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-2792
- looks good initially, want to review closely by pull down
- minor state issue to update data
  - add state
  - reload data
- see pattern on license picklist (see afterQuery call change)

QA / UAT

Jira Legacy
server System JiraJIRA
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-3121

Release Candidates

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

For Release / Awaiting Deployment

NA

Pending Testrails

Jira Legacy
server System JiraJIRA
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-3062
Jira Legacy
server System JiraJIRA
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-1910
Jira Legacy
server System JiraJIRA
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-3119
Jira Legacy
server System JiraJIRA
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-3120

Closed: Quesnelia R2024.1

Stories / Bugs

Jira Legacy
server System JiraJIRA
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-3073
/
Jira Legacy
server System JiraJIRA
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-3072
Jira Legacy
server System JiraJIRA
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-3123

Maintenance / Tasks

Release Tasks

Closed (No ERM Release)

Testing Tasks

NA

<10 mins

AOB

New Issues

NA

Added to sprint

Jira Legacy
server System JiraJIRA
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key ERM-3124

Versions Compared

Old Version 5

New Version Current

Key

Meeting Details

Goals

Participants

Apologies

Discussion items

In Progress

Blocked

Needs Elaboration / Triage

Sprint Backlog - Next Up

Sprint Backlog - to follow

Code Review:

QA / UAT

For Release / Awaiting Deployment

Pending Testrails

Closed: Quesnelia R2024.1

Maintenance / Tasks

Release Tasks

Testing Tasks

Added to sprint

Not added to sprint

Other

Component Updates

Release Planning

Testing

Security

Page Comparison

Versions Compared

Old Version 5

New Version Current

Key

Meeting Details

Goals

Participants

Apologies

Discussion items

In Progress

Blocked

Needs Elaboration / Triage

Sprint Backlog - Next Up

Sprint Backlog - to follow

Code Review:

QA / UAT

For Release / Awaiting Deployment

Pending Testrails

Closed: Quesnelia R2024.1

Maintenance / Tasks

Release Tasks

Testing Tasks

Added to sprint

Not added to sprint

Other

Component Updates

Release Planning

Testing

Security