Why: Prokopovych will disband once Orchid is released. A new team(s) must be assigned to own/release inventory modules.
Plan: Spitfire and Folijet co-own modules and backlog
Transition date: Orchid GA date
Responsible for Orchid hotfix/service patch: Yes
Poppy expectations:
- No new functionality.
- Developers' focus is on acquiring knowledge especially around the release process with so many contributors.
- QA's focus is on acquiring knowledge and defining a plan for managing these additional modules/workflows.
- PO's focus is on reviewing backlog and evaluating work for Q and R releases
- Only address P1 issues and if possible P2.
- May need to address MODINVSTOR-960 - Getting issue details... STATUS but details are unclear.
Transitioning back-end modules
| module | New Owner | Support |
|---|---|---|
| mod-inventory | Folijet | Marc Johnson |
| mod-inventory-storage | Spitfire | Marc Johnson |
Transitioning front-end modules
| module | New Owner | Support |
|---|---|---|
| ui-inventory | Folijet | Michal Kuklis (will be available until June 30 to help with release) |
| ui-plugin-find-instance | Spitfire | Michal Kuklis (will be available until June 30 to help with release) |
| ui-plugin-create-inventory-records | Folijet | Michal Kuklis (will be available until June 30 to help with release) |
https://wiki.folio.org/display/REL/Team+vs+module+responsibility+matrix
Useful Jira filters
- Prokopovych unclosed issues (no epics, umbrellas, new features) - note that this includes ALL modules, not just Inventory-related ones: https://issues.folio.org/issues/?filter=15187 (449)
- P1/P2 issues (21 issues)
- P3/P4 issues (245 issues)
- TBD/None issues (177 issues)
- Prokopovych unclosed Inventory issues (no epics, umbrellas, new features): https://issues.folio.org/issues/?filter=15188 (396)
- Prokopovych unclosed Inventory bugs (no epics, umbrellas, new features): https://issues.folio.org/issues/?filter=15189 (36)
Backlog management
- POs will review above backlog and will only move items as ready to do so.
- There maybe times that Spitfire PO will assign work to Folijet and vice versa.
Proposed way to break up work
Spitfire
- Inventory search and browse
- Select an instance record via plug-in
Folijet
- CRUD Instance
- Fast add instance/holdings/item plug-in
- CRUD Holdings
- CRUD Items?
- Settings
Potential UX work over the next couple of releases
- Replace Inventory search and sort with react?
- Replace search facets
- Improve interacting with long lists
- Hide fields support
- Template support
- Add a link to search documentation
Questions
- What additional help is needed to make this transition go smoothly?
- Folijet: 1 Backend developer (what level? - Kate will make recommendation) | Frontend developer (what level? - Ivan will make recommendation): TBD based on RTL/Jest conversation | TBD : Manual QA? | TBD : AQA
- Spitfire: TBD : Manual QA? | TBD : AQA
- Confirm Karate tests coverage – speak with Marc
- What about RTL/JEST remaining work?
- NES still working on it? What do we need to do?
Action items
- QAs: Transition AQA test cases (Natalia and Ivan can schedule a meeting to discuss plan)
- QAs: Transition manual QA test cases (Natalia and Ivan can schedule a meeting to discuss plan)
- KG: Communicate change to community
- KG: Address the RTL/Jest situation with LeeB.
- KG/AMB: Review P1/P2 Prokopovych issues
- AMB - will come up with a plan for backlog organization
- Reassign Karate tests to Spitfire and Folijet
- Each team creates a story to reassign mod-inventory and mod-inventory-storage
- Each team review Poppy features capacity based on #5. Possibly create another feature for this work.