| Time | Item | Who | Notes |
|---|
| 5m | Agenda and action item review | Josh |
|
| (potentialnext call) | Orderable versioning | Chongsun Ahn (Unlicensed) | - Continue the show and tell on the how
|
| (potential)15m | Feature flags | Josh Zamor and Sebastian Brudziński and Mateusz Kwiatkowski | - Do we think this is mature yet? Can it be used to make quick, unplanned, releases of a service? Do we all understand it?
|
| (potentialnext call) | Followup on audit log initializer |
| - We completed
| Jira Legacy |
|---|
| server | System JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 448ba138-230b-3f91-a83e-16e7db1deed1 |
|---|
| key | OLMIS-3078 |
|---|
|
which will help production data sets, however for demo data we would still iterate over all the demo data records on the first start as they don't have snapshots yet. Is a slow startup still / more an issue? With the increased size of the demo data that we're adding, and thoughts to have millions of records, do we think we have an issue?
|
| (potentialnext call) | DHIS2 followup on how (not ready) |
| |
| 5m | Team City | Wesley Brown |
|
| 25m | Reference Data Seed Tool - maintenance plan | Sebastian Brudziński | - Reference data seed tool seem to be getting used more frequently and outside of MW
- We currently do not have a process to verify the tool works after releasing
- How do we ensure that everything works after a new release? An automated test? Manual regression check as a part of release?
|