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.

•  (The approach described in the comments seems correct — as long as the service validates and is the absolute source of information, that all good)
•  
•  (is this worth doing? enough benefit?)
•  (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?
• 
• 
• ??? Geo data  ???
  
  

UI

Bugs 

New Stuff

• 
• 
• New user setup and administration - Need to talk about workflow with modals (Nick and Sam)
• ??Other administration screens??
• 
•  
• 
•  (Nick to simplify this ticket)
• 
• 
• Migrate other modals to use OpenLMISModalService

Stretch Goals

Dev-UI

• Make watch build just files that changed
• Add Live Reload

Nick - are 1907 and 1908 a priority? 

Platform

• ?
•  should this go into the sprint? What component?
  
  

Component leads, are any of the following time sensitive or still needed??

 can we move forward with this? Can SolDevelo do it?

 (is this ILL or SolDevelo?)

 is this still needed?

Team ILL

•  (Team ILL; Brandon is willing to write up/diagram a few options and bring to a group conversation including Team Panda, Josh, Mary Jo)
•  (any follow-up needed?)
•  (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)
•  or  or similar?
• 
• 

Plus there are lots of good ideas from the Holding Off section at the bottom of Backlog Grooming Sprint 22