<5 mins | Introductions | |
| Call Priorities | - Add test to stripes-kint-components to check encoding of special characters
Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | STRIPES-834 |
---|
|
- ERM-2613 to ERM-2618
- EF to review with ZB
- Stripes have merged work without input from the team.
- Backend on Linux - expected to be up and running end of today
- Jira down - issue specifics not available.
|
| WIP Expand |
---|
| - 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-2611 |
---|
| / Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-2610 |
---|
|
- Progress / Impediments:
- Some issues to find the example PR 555
- ERM-2610 in QA
- Moved onto ERM-2611
- Help or input needed:
- Is the primary slug the Gokb UUID?
- Not currently, but will be going forward.
- Therefore it appears twice in item header
- Alternate slugs should be an array with >1 entry.
- This is for future proofing, and should be tested
- But for Gokb, they will only have one.
- Should package_shortcode in GOKbdAIAdaptor.groovy log entry routine be removed?
- Yes, an replace with gokb_uuid check instead. Package_shortcode is used when no reference is used. Removing it means we expect and have to assume a new package.
- ETA for review: Wed 25 Jan(?)
Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-2514 |
---|
|
Progress / Impediments: TODO: New unknowns: Help or input needed: Does this need backporting for Nolana or Morning Glory?
ETA for review:
|
| Pending Expand |
---|
| - ISSUE
- Blocking conditions
- Action needed
|
- Are the blocking conditions still relevant?
- What action is needed to unblock, and by whom?
Expand |
---|
| - 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 / Triage Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-2474 |
---|
|
Sprint Backlog - Next Up Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-2514 |
---|
|
Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-2547 |
---|
|
Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-2549 |
---|
|
Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-2538 |
---|
|
Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-2540 |
---|
|
Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-2550 |
---|
|
Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-2611 |
---|
|
Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-2488 |
---|
|
Allocations- Claudia: NA
- Ethan: ERM-2514, backports
- Monireh: Set up backend environment in Linux
|
| 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: Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-2449 |
---|
|
Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-2534 |
---|
|
QA / UAT Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-2569 |
---|
|
- Add backport / release issue for Nolana
- Add backport / release issue for Morning Glory
Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-2467 |
---|
|
Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-2482 |
---|
|
Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-2554 |
---|
|
Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-2555 |
---|
|
|
| Release Candidates - What has passed QA since last dev call?
- What has been closed since last dev call?
| For Release / Pending Testrails Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-2449 |
---|
|
Closed: Orchid R2023.1Stories / BugsRTL / Tasks Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-2589 |
---|
|
Closed (No ERM Release) |
| AOB
| New Issues Added to sprintNot added to sprint Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | ERM-2619 |
---|
|
OtherComponent Updates- internal contacts and organisations need to be moved away from stripes-connect
Release PlanningTestingSecurity- flag possible vs confirmed dependency issues
- need to review internal handling process
|