Openmrs platform 2.2-alpha Release Impending

[samuel34 (Samuel Male)]

@dkayiwa

if you created the tag manually, can you delete it?

True that! I just ran.

git tag 2.2.0-alpha

And yes I hav deleted it.

@dkayiwa

Then use the CI plan to release, and set the release version as 2.2.0-alpha and the next development version as 2.2.0-SNAPSHOT

How really!

This is the page I get if I think of triggering any release with CI

• Is it the right page
• If true, I’m supposed to override the maven variables
• If not, How and where do you set release and next development versions and how sure should I be that the release CI build creates the git tag automatically?

The criteria you have gave ain’t clear since it also alters from OpenMRS Platform Release Process - Documentation - OpenMRS Wiki @dkayiwa

cc: @mogoodrich

[dkayiwa (Daniel Kayiwa)]

Yes you can override variables from there. Or go under “Actions”, “Configure plan”, then go to the variables tab to set their values: https://ci.openmrs.org/chain/admin/config/configureChainVariables.action?buildKey=TRUNK-OC2X

[mogoodrich (Mark Goodrich)]

@samuel34 thanks for doing this and @dkayiwa thanks for guiding him through it… I just skimmed the thread, but hopefully can review in greater detail later today…

[dkayiwa (Daniel Kayiwa)]

It turns out that 2.2.0-alpha as the release version is not accepted by our CI
[ERROR] Version 2.2.0-alpha is not semver, e.g. 4.25.0. Check http://semver.org/

https://ci.openmrs.org/browse/TRUNK-OC2X-6/log

@cintiadr do you know where we should edit to allow this?

[dkayiwa (Daniel Kayiwa)]

OK here it is: https://github.com/openmrs/openmrs-contrib-bamboo/blob/63acfae3024f50d743ed89da44c014b3f2c7cff6/release-prepare-perform.sh#L42

But would you even recommend such a modification?

[cintiadr (Cintia Del Rio)]

releasing modules using semantic versioning

Dear all! as stated here https://wiki.openmrs.org/display/docs/Versioning OpenMRS uses semantic versioning http://semver.org/ which A normal version number MUST take the form X.Y.Z where X, Y, and Z are non-negative integers, and MUST NOT contain leading zeroes. X is the major version, Y is the minor version, and Z is the patch version. but I often encounter modules which do not include all 3 parts of the proposed major.minor.maintenance style. @dkayiwa you released the 1.0 of https://g…

OpenMRS Reference Application 2.6 Release

For everyone doing releases: Now bamboo release scripts enforce semver: releasing modules using semantic versioning Also, if you release, let’s say 2.3.0, the next snapshot should be 2.4.0-SNAPSHOT. If you don’t override the development.version variable, the script will automatically determine that for you.

Well.

[reubenv (Reuben Varghese)]

You guys are really awesome, thanks for doing this ! I just realised that I have a lot left to learn

[cintiadr (Cintia Del Rio)]

@dkayiwa in order to have this release out, easiest one is to comment those lines in the script, push, run a whole new build, do the release, and revert your commit. Note that it absolutely needs to be a new build number in bamboo, it cannot be just the release stage, ad commit hashes are locked on the first stage.

In order to fix it properly, I think we should decide the versioning schema for ‘non-modules’. I don’t mind here, but we need to agree.

Then we need to decide on how to identify modules (pure semver) and non-modules. Is it doable by the git URL or do we pass a flag to the script like ‘-p’ (for product versioning)?

I think that when we added semver, we only had modules using the script.

[dkayiwa (Daniel Kayiwa)]

Yes i had temporarily allowed alpha https://github.com/openmrs/openmrs-contrib-bamboo/commit/88c804f1da6143fe9bc0737eb8de78d56ac59c2b which i have reverted after the release https://ci.openmrs.org/browse/TRUNK-OC2X-7

@samuel34 can you do pull requests in the restwebservices and coreapps modules with the versions changesd from 2.2.0-SNAPSHOT to 2.2.0-alpha?

[dkayiwa (Daniel Kayiwa)]

@samuel34 can you do the same for the emrapi module?

[samuel34 (Samuel Male)]

Finished at https://github.com/openmrs/openmrs-module-emrapi/pull/158

[mogoodrich (Mark Goodrich)]

Looks like this means we will need to release EMR API again? (Should be straightforward).

[dkayiwa (Daniel Kayiwa)]

@samuel34 do you have time to release openmrs core platform 2.0.7?

https://ci.openmrs.org/download/RESTWS-RESTWS-RTM/build_logs/RESTWS-RESTWS-RTM-790.log

[samuel34 (Samuel Male)]

Definitely I’m gonna buy time tonight and make the release

[dkayiwa (Daniel Kayiwa)]

@samuel34 because this was blocking the release of the webservices.rest module which was needed here Question about webservices.rest release date i have just done the CI part of the release for core 2.0.7 to make the dependencies available to compile and release the module. Are you able to continue with the remaining steps for the release of platform 2.0.7?

[samuel34 (Samuel Male)]

Assured man.

Thanks for the follow up @dkayiwa

[reubenv (Reuben Varghese)]

Hey, I was wondering if the 2.2 platform Alpha was ever released. We have a final pair of modules that have this as a dependency. If not, how do you suggest that we go about releasing those 2 modules(core apps and EMR API)?

Thanks!

Cc: @dkayiwa @mogoodrich @samuel34

[dkayiwa (Daniel Kayiwa)]

@reubenv I have just released both modules. So you should be able to proceed.

[reubenv (Reuben Varghese)]

Thanks a ton @dkayiwa! You rock

[c.antwi (Cynthia Antwi)]

Good Morning

Have we completed testing on this ? Is it ready to be released? When can we announce?

to the release managers @irenyak1 @samuel34 @tendomart we need to compile a report / release notes of the new features developed etc.

Can we do a brief call on Uberconference today 20 Feb at 3pm EAT?