...
Attendees
- Jeff Xiong (Unlicensed)
- Darius Jazayeri (Unlicensed)
- Pengfei Cui (Deactivated)
- Paweł Nawrocki (Deactivated)
- Nikodem Graczewski (Unlicensed)
- Sebastian Brudziński
- Ben LeibertChongsun Ahn (Unlicensed)
- Brandon Bowersox-Johnson
Goals
...
| Pro | Con |
|---|---|
| Makes just the change/work that's needed | Consumers will eventually have to do the work when the deprecated operations are removed |
| Doesn't break the contract, consumers still work | Will have to maintain both endpoints while they both exist (fixing bugs, refactor?) |
We would think that we would phase out the deprecated operation in the next MAJOR release, though a set amount of minimum support time (e.g. 6 months) might be preferable.
#3, Do all the work NOW - and release the new major (uber) version
...
| Pro | Con |
|---|---|
| Big bang - everything is fixed (we could more things) | Breaks the contract, so the semantic version has to be increased, and all consumers have to do work to account for the change - to all the resources |
| Ref Data service would be more consistent - cognitive load | Resource intensive - this scope of work may require a team (small) to go through and make all the changes. Also all other components may need more human resources |
| We may do work that's un-needed. Maybe supply lines will never need extra data. Stock adjustment reasons may go away, replaced with stock management service. | |
| We may not really prevent the major version from being incremented rapidly. |
Moving from GET to POST for search, and implementing pagination for search, could reduce people resources for making reference data better (maybe half the work). Consumer LOE would stay the same.
Malawi - Extension for average consumption
Average Consumption calculation - extension analysis
Notes
Action items
Some question about the LineItemFieldsCalculator calculations and the delegating class - feels weird to have both
How does the data get back to the UI?
- Is it an extension to the calculation class? Or an extension to getting previous requisitions? Or both?
- If it's just the previous requisitions, then if the configuration is the previous N years
Next steps:
- check to see if previous requisition approach (returning N in DTO) is feasible
- mature the document (specific ext approach, actions and timeline, containers and packaging) - ping technical forum
- tech comm to review future draft
Action items
- Josh Zamor to throw up voting for Reference Data poll of the forum (everyone votes by wed/thur)
- Sebastian Brudziński to continue maturing Malawi Ext. Proposal for Average Consumption. Post to technical forum for intermediate feedback
- Sebastian Brudziński to remind technical committee to discuss new draft document at next committee call (May 2nd)