I will release OpenMRS Core 2.1.1 ahead of the the release of Bahmni 0.90.
Any objections / comments / …?
1 Like
No objection from me and i would love to see your release power the soon coming release of the reference application. @ssmusoke
@dkayiwa there are 3 open JIRA tickets associated with Core 2.1.1 (here), could you look into what to do with them?
None of them has committed code. Just remove the fix version from each of them.
Fine with me, thanks for taking on the release!
@dkayiwa , I’m trying to figure out what is to be done outside of releasing from Bamboo.
(Q1.) Should the war be uploaded to SourceForge? More generally, is anybody still using SourceForge?
(Q2.) There were no releases notes for 2.1.0… can I assume that there won’t be any for 2.1.1.
According to this, we still upload to SourceForge: https://wiki.openmrs.org/display/docs/OpenMRS+Platform+Release+Process
That was a mistake. Every platform or core release should have release notes.
Since this is just a Core release, should this be called ‘Core Release Notes 2.11.1’ or ‘Platform Release Notes 2.11.1’?
I found the culprit 
I was wrong, there were release notes: Core 2.1.0 Release Notes.
@dkayiwa, I couldn’t release as the build is suddenly failing on Bamboo. I re-ran the build, but in fact it had already failed since this PR was merged.
See https://ci.openmrs.org/browse/TRUNK-TWOONEX-JOB1-52/log
I could build it locally (on macOS), any idea why this is happening on the CI?
@shruthipitta, this might delay things a little.
That failing test seems flaky, we probably need to address it, might be complex to fix though, we can add @Ignore to it and create a ticket to have it fixed at a later point for the sake of getting you unblocked and the builds to being consistently green.
The thing is, that test is precisely the one validating one of the new features in this minor release: TRUNK-5213.
On master the same problem occurred, however there you could get things back to normal with another manual run.
@mksd is this what you need to proceed? https://ci.openmrs.org/browse/TRUNK-TWOONEX-54
Yes, thank you! What did you do?
Just launched the release job, let’s see how it goes: https://ci.openmrs.org/browse/TRUNK-TWOONEX-REL-54
Done! See ‘Core Release Notes 2.1.1’.
However, I can’t figure out how to upload stuff to SourceForge, what’s the trick again?
P.S. @cintiadr FYI there is an issue in Confluence, the JIRA filters show an authentication issue. Example:
I had the impression I might have broken the applink between JIRA and confluence when I was trying to fix the new JIRA instance. As we should have just one instance from next weekend, I do hope the problems might go away.
All you need is a sourceforge account, make sure the OpenMRS project is added to your account to be able to upload files in its space.
So in fact one needs to first add his/her public key into Account Settings \ SSH Settings (here at the time of this writing.)
Then this:
rsync -avP -e ssh /path/to/your/release/folder
mksd@frs.sourceforge.net:/home/frs/project/openmrs/releases
No trailing slashes on either end, and replacing ‘mksd’ if you’re not me
To be clear with no trailing slashes on either end, folder will be copied into releases.
@wyclif, regarding your comment on Confluence. How do I run the SQL differences between 2.1.0 and 2.1.1?
I thought there is no DB changes between 2.1.0 and 2.1.1, by convention there should be no DB changes in a minor release. Anyways, the database changes are automatically applied at module startup by the module engine, you don’t need to do anything.
Sorry I was unclear. I meant, if I don’t know what database changes might have happen, what tool can I use to tell me what database changes were brought between two versions?
Here I strongly suspect that there aren’t any, but how can I be sure?