Together with Soldevelo team, we would like to invite you for 5th sprint review. Details of the event are stated below:
cc: @jslawinski, @pgesek, @darius, @dkayiwa, @raff, @mseaton
- Darius Jazayeri
- Mike Seaton
- Daniel Kayiwa
- Jakub Slawinski
- Paweł Gesek
- Daniel Serkowski
- Arkadiusz Lalo
- Przemyslaw Kornowski
- Jakub Trzebiatowski
- SYNCT-71: Improve audit message details.
- SYNCT-30: The logic for retry messages.
- SYNCT-72: Improve details about failed push operation.
- SYNCT-60: Location object Pull & Push.
- SYNCT-57: Scheduler for Pull & Push.
- Still in progress:
- SYNCT-67: User object Pull & Push
- SYNCT-65: Privilege Object Pull & Push
- SYNCT-58: Person Object Pull & Push
The situation when instance pulls the object that you just push it to parent shouldn’t take place. Conversation will be placed here: https://issues.openmrs.org/browse/SYNCT-75
The work on tickets that attention or tracking of other people is needed should be followed by them. One of the solutions is attaching these people under for example JIRA’s tickets.
Objects should be synchronized with their UUIDs. On each instance, the same object should have the same UUID. Ticket: https://issues.openmrs.org/browse/SYNCT-76
If there are changes in some modules, the information about that and maturity of these modules should be placed for example on OpenMRS’s Talk. It will be helpful trace changes and will increase the number of tests and usages of them.
The main goal of next sprints is providing the MVP, that should, for example, synchronize patients. It is also important to specify the scope of the MVN synchronization exactly - it can’t consist of all OpenMRS objects and it should be organized in a shared document. Current synced fields. https://issues.openmrs.org/browse/SYNCT-79
Video: OpenMRS Sync 2.0 Sprint 5 Review.
cc: @darius, @mseaton, @dkayiwa, @raff, @jslawinski, @pgesek, @alalo, @dserkowski, @jtrzebiatowski