| <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 |  - Are the related FAT issues supposed to be
Closed also?
 - grails-okapi release decision?
 /  - release or wait? follow-up to confirm go-ahead with Steve.
|
| WIP - 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 - Progress / Impediments:
- getting stuck on deployment
- 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)
- Progress / Impediments: blocked
- TODO: release
- Help or input needed: branch release of KIWT
 - 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
 - Progress / Impediments:
- udaed
- assigned to Steve for QA
- TODO:
 - Progress / Impediments:
- 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
 - api mapping and requirement details added
|
| Pending - ISSUE
- Blocking conditions
- Action needed
|
- Are the blocking conditions still relevant?
- What action is needed to unblock, and by whom?
- 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?
- Who is picking up what next?
- When is next issue expected to start / complete?
- Anything needed to start next issue (dependencies or clarifications)?
| BlockedNeeds Elaboration / TriageSprint Backlog - Next UpAllocations - Claudia:
- Ethan:
- Jack:
- Monireh:
|
| 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 followSprint Backlog - At Risk Removed |
| In Review - Any impediments to review or QA?
- Any useful context, implementation choices or limitations for the reviewer/tester to know ?
| Code Review: - looks good initially, want to review closely by pull down
- minor state issue to update data
- see pattern on license picklist (see afterQuery call change)
QA / UAT |
| Release Candidates - What has passed QA since last dev call?
- What has been closed since last dev call?
| For Release / Awaiting DeploymentPending TestrailsClosed: Quesnelia R2024.1Stories / Bugs Maintenance / TasksRelease Tasks
Closed (No ERM Release) Testing Tasks |
| AOB
| New Issues Added to sprintNot added to sprintOtherComponent UpdatesRelease PlanningTestingSecurity |