Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
Version 1
Next »
Discussion items
Time | Item | Notes |
---|
<5 mins | Introductions | |
| Call Priorities | -
ERM-2064
-
Getting issue details...
STATUS
|
| 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-2630
-
Getting issue details...
STATUS
- Progress / Impediments:
- TODO:
- get endpoints accepting/logging out json input
- started
- not wired through okapi as shape uincertain
- can hit locally, passsing list of packages and log them out to a package schema
- therefore package schema is accepting this approach
- split schema to interdependently (1) expect and (2) not expect ...
- wire schema into ingest process
- dig into ingest process to plan refactoring
- New unknowns:
- Help or input needed:
- Input needed from Ian to understand legacy technical decisions around, eg, remote kb, source/ref push/pull
- To follow up on Thursday with Ian re domain model and shape of future shape/behaviour of external service
- 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?
- 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-2645
-
Getting issue details...
STATUS
Needs Elaboration / TriageSprint Backlog - Next Up-
ERM-2064
-
Getting issue details...
STATUS
-
ERM-1026
-
Getting issue details...
STATUS
-
ERM-1061
-
Getting issue details...
STATUS
-
ERM-1795
-
Getting issue details...
STATUS
Allocations |
| 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:-
ERM-2879
-
Getting issue details...
STATUS
QA / UAT -
SI-12
-
Getting issue details...
STATUS
-
ERM-2612
-
Getting issue details...
STATUS
-
ERM-2633
-
Getting issue details...
STATUS
/
ERM-2624
-
Getting issue details...
STATUS
/
ERM-2625
-
Getting issue details...
STATUS
|
| Release Candidates - What has passed QA since last dev call?
- What has been closed since last dev call?
| For Release / Pending Testrails-
ERM-2643
-
Getting issue details...
STATUS
-
ERM-2506
-
Getting issue details...
STATUS
Closed: Poppy R2023.2Stories / BugsMaintenance / TasksRelease TasksClosed: Orchid R2023.1 BugfixRelease Tasks
ERM-2648
-
Getting issue details...
STATUS
-
ERM-2640
-
Getting issue details...
STATUS
-
ERM-2649
-
Getting issue details...
STATUS
Closed (No ERM Release) |
| AOB
| New Issues -
ERM-2880
-
Getting issue details...
STATUS
Added to sprint-
ERM-2879
-
Getting issue details...
STATUS
Not added to sprintOtherComponent UpdatesRelease PlanningTestingSecurity |