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
« Previous
Version 3
Next »
Meeting Details
Date |
|
---|
Time | 09:30am ET, 2:30pm UK, 3:30pm Germany |
---|
Location | Video Call in FOLIO Slack: #erm-developers |
---|
Discussion items
Time | Item | Notes | Action Items |
---|
<5 mins | Introductions | | |
30 mins | Demos | - In Development
- In Code Review
- In QA / Accepted
| |
10 mins | Sprint Completion | - Merge Cutoff
- Items at Risk / Spillover
-
ERM-162
-
Getting issue details...
STATUS
-
ERM-189
-
Getting issue details...
STATUS
-
ERM-184
-
Getting issue details...
STATUS
| |
10 mins | Upcoming Sprint | See ERM Next Sprint Candidates list in https://issues.folio.org/secure/RapidBoard.jspa?rapidView=89&view=planning.nodetail |
|
5+ | AOB | - Previous Actions
- Bootstrapping data:
- taking it out of module to not require code changes but use data scripts
- will still be an issue for bootstrapping users (ERM-49) - to be considered in ongoing conversations
- Developer onboarding:
- 'Office hours' `carried over`
- Changes to Team Updates in #erm-updates
- FOLIO Meetup Washington 17-19 June
- not having a fringe dev gathering
- looking at doing this early Q3
- date options TBC
| - Set up onboarding feedback session for next week.
|
Sprint WIP Demos
Delivery Board: https://issues.folio.org/secure/RapidBoard.jspa?rapidView=89
Feature | Issue | Who | Notes / TODO |
---|
UXPROD-1520
-
Getting issue details...
STATUS
|
ERM-162
-
Getting issue details...
STATUS
| | ? |
UXPROD-1520
-
Getting issue details...
STATUS
|
ERM-163
-
Getting issue details...
STATUS
| | Pending ERM-163 |
UXPROD-1660
-
Getting issue details...
STATUS
|
ERM-197
-
Getting issue details...
STATUS
| | Stuck In Code Review because of build issue with GBV test - Progress to In QA for , testing on folio-snapshot or folio-testing.
|
UXPROD-1660
-
Getting issue details...
STATUS
|
ERM-198
-
Getting issue details...
STATUS
| | |
UXPROD-1159
-
Getting issue details...
STATUS
|
ERM-184
-
Getting issue details...
STATUS
| | Determine where/how to
ERM-209
-
Getting issue details...
STATUS
- To store in db to circumvent OKAPI non-persistence issue.
- Example
- median individual file size: ~345kb
- from Benjamin: 10 years, 1000 files, 800mb total
- Some organizations may use cloud storage going forward
- could be worth abstracting implementation from outset, but not to be done this time round
|
|
ERM-199
-
Getting issue details...
STATUS
| | - Final set of tests expected to be completed today
|
|
ERM-189
-
Getting issue details...
STATUS
| | Not progressed |
UXPROD-1300
-
Getting issue details...
STATUS
|
ERM-211
-
Getting issue details...
STATUS
| | ? |
|
ERM-92
-
Getting issue details...
STATUS
| | Integration tests are pending, but generator is finished. - PR to be submitted for work completed so far.
- Integration tests to be resolved separately.
|