@mozzy a sprint is not open ended. Each sprint has a fixed end date which is not a moving target. Did you get a chance to look at these?
https://wiki.openmrs.org/display/RES/Development+Sprints
https://wiki.openmrs.org/display/RES/How-To+Have+a+Sprint
https://wiki.openmrs.org/display/RES/How+To+Do+A+Sprint+Demo%3A+The+A+-+Z+Guide
Surely let me plan so we have a sprint Demo
Hello participants , i want to thank you for all the work you have done upgrading our libraries. Now in prepartion for our sprint demo ,though it has come a litle bit late , i woud like to inform all those that had their Prs merged and their tickets closed , to do a little research on the impact of their changes ,thats is say improving security ,etc . NB this can be done by reading a little further on the release notes of the different dependencies that were upgraded.So that each participant can present in the Demo a summary of the siginificance and impact of of their changes that were merged. Thanks
cc
Hey Everyone!
The time that everyone has chosen in 18 June 2019 at 11am on https://www.uberconference.com/openmrs
UTC or EAT ?
It will be UTC timezone
To make more emphasis ,Since we are not going to make any GUI demo , the following people will present the impact of the library upgrade that they did. More information can be read from the each library’ release notes .
@jwnasambu will present about the impact of
@odorajonathan will present about the impact of
@georgejr will present about the impact of
1.
upgrading org.dbunit:dbunit
The rest of the mebers will present the challenges and blockers faced on the library upgrades they attempted
cc
Time is 11 am UTC or 2pm EAT
The presentation about each library should be a summary of how the library upgrade affects openmrs say in terms of security , and probably key features added in the upgraded library
Can we post the presentations here so those of us who cannot be on the call can view the presentations and comment/question?