MJ Note : Discussed releasing another patch release at the end of this sprint as well. This will allow us one more sprint to get in needed extension points, bugs and more admin screens. Please keep this in mind when planning for sprint 23.
Requisition
We expect version 3.1.0 will already have been released around Tuesday, March 28. After that, we will proceed with 3.1.1-SNAPSHOT to do bug fixes, performance, security, & refactoring.
- - OLMIS-2158Getting issue details... STATUS (Need discussion with Josh and Mary Jo on LOE and choosing an approach; see comments.)
- - OLMIS-1979Getting issue details... STATUS
- - OLMIS-1780Getting issue details... STATUS (is this worth doing? enough benefit?)
- - OLMIS-1391Getting issue details... STATUS (is this worth doing? enough benefit?)
Reference Data
- Lot Management API endpoints (Stock Team Panda needs this ASAP! Josh Zamor We have this wiki page that maps out proposed Lot Management endpoints, but we need your review and we need to turn this into tickets for Teams AYIC/TOP to code as a top priority after 3.0.1 ref-distro release.)
- Any other bugs or issues Pengfei had with ReferenceData endpoints that need to change for Stock to proceed?
UI
Bugs (if any)? Admin screens?
- - OLMIS-2126Getting issue details... STATUS
- - OLMIS-2103Getting issue details... STATUS
- - OLMIS-2137Getting issue details... STATUS
- - OLMIS-2156Getting issue details... STATUS
- - OLMIS-2142Getting issue details... STATUS
- - OLMIS-2161Getting issue details... STATUS
We could start on the autosaving usability improvements
Nick - are 1907 and 1908 a priority?
What about - OLMIS-1687Getting issue details... STATUS and - OLMIS-1923Getting issue details... STATUS ?
- OLMIS-1925Getting issue details... STATUS
Admin screens
Should be working on roles - OLMIS-1271Getting issue details... STATUS
Platform
- - OLMIS-1972Getting issue details... STATUS ?
-
-
OLMIS-2155Getting issue details...
STATUS
should this go into the sprint? What component?
Component leads, are any of the following time sensitive?
- OLMIS-1853Getting issue details... STATUS
- OLMIS-1444Getting issue details... STATUS can we move forward with this? Can SolDevelo do it?
- OLMIS-2111Getting issue details... STATUS
- OLMIS-2074Getting issue details... STATUS
- OLMIS-1707Getting issue details... STATUS
- OLMIS-1994Getting issue details... STATUS (is this ILL or SolDevelo?)
- OLMIS-1689Getting issue details... STATUS is this still needed?
Team ILL
- - OLMIS-2113Getting issue details... STATUS (Team ILL; Brandon is willing to write up/diagram a few options and bring to a group conversation including Team Panda, Josh, Mary Jo)
- - OLMIS-2166Getting issue details... STATUS (any follow-up needed?)
- - OLMIS-1997Getting issue details... STATUS (we explained versioning to Tech Committee and SolDevelo, but we should update the wiki to capture it—especially that the components are semantically versioned, but the ref-distro uses milestone version numbers; and document that we prefer to coordinate working on master towards one common goal, namely the next release, in order to avoid the added effort of branching; Brandon has some paper notes and is willing to write a draft, but I believe it would really be Josh and Tech Committee that would finalize/approve)
- - OLMIS-2162Getting issue details... STATUS or - OLMIS-2160Getting issue details... STATUS or similar?
- - OLMIS-2167Getting issue details... STATUS
- - OLMIS-2168Getting issue details... STATUS
Plus there are lots of good ideas from the Holding Off section at the bottom of Backlog Grooming Sprint 22