We’re committing to the coreapps master branch during the Patient Summary Widgets sprint. It has some work in progress widgets, which we need to disable before you release. Let us know when you want to do that.
We need to use semantic versioning correctly. It’s a maintenance version if it only includes bugfixes; if it includes new features, it’s a new minor version.
coreapps definitely has new features, so when we do release it it needs to be 1.12.0 (not 1.11.2).
The other three should move to semantic versioning numbers on this next release:
@ssmusoke, reigstrationapp is looking good now… there were three problems I ran into. One was something I had to fix in our own configuration code, another was a bug I fixed here:
… and the other was a change that introduced a bug that I just reverted for now, referenced here:
I am still having trouble releasing EMRAPI 1.21.0, @darius bumped up the minor version due to new features - metadata mapping, and the adding encounters without visit
@raff I will hold off coreapps until the sprint is done - I think its better that way
@ssmusoke for emrapi, whenever you were releasing, the DateMapperTest test was failing. I suspect the release scripts are using openjdk 7 on which that test is known to fail. I tried to switch to it to confirm, but the build just froze.
@ssmusoke, the work on widgets is done and coreapps is ready for a minor release.
We’ll need to release webservices.rest and data integrity module for the new widgets to work properly. Would you have time to do that as well or you need help?
@raff All releases done except web services which requires some gymnastics disabling support for OpenMRS 2.1, releasing, then re-enabling it. Please help with that one
Also note that I had to release uicommons 2.2.0 in order to be able to release coreapps, fortunately Bamboo does not allow snapshot versions as I had not seen this dependency.