Question: In reference data, how do we want to handle adding pagination and extra data to resources in semantic versioning
Answer: One big fat release
Next Step:Josh Zamor will write a "stub" JIRA ticket
Notes
Malawi
Extension Pt Process
Communicate out to developer forum
describe use-case
describe proposed extension points - be detailed about method signatures, it's a Java interface
solicit feedback - process and need should be non-controversial so long as the service 1. doesn't become a jumble of things and 2. it doesn't break backwards compatibility
Develop extension point
Anyone could develop the extension point, either he or she whom proposed it, or someone that works on the Service
Extension point should be a Pull Request that's easy to merge in - conforms to Service style guide, consistency, etc and passes all tests.
The one that proposed the use-case, should implement the extension module
Implementation should expect to wait until next Release
Implementer should expect to need to wait at least a month (a couple sprints) - to give Service time to plan their release
Implementer can speed things along by submitting the extension point themself
If the request comes right before the next release, e.g. a week before it ships, implementer should expect to wait until the next release
Implementer could choose to take on more risk by submitting the PR, getting it merged, and then adopting the in-development Service. Risky and buyer-beware, but might feel faster.
Next step: LOE exercise to determine if we can fit this much work into the next release - Reference Data would be under active development and all consumers of these search endpoints may also need to become active to adjust to these changes.
Action items
Sebastian Brudziński send email to dev-forum about how to handle batch errors as 200 or 400 status code