Hey,
I would like to announce the next platform maintenance release in the 2.1.x series.
Well I just wanna be sure of the bundled modules and their artifacts.
cc: @dkayiwa
Hey,
I would like to announce the next platform maintenance release in the 2.1.x series.
Well I just wanna be sure of the bundled modules and their artifacts.
cc: @dkayiwa
I have cross checked and it was only the webservices.rest module which was not updated to the latest version. Just done that https://github.com/openmrs/openmrs-distro-platform/commit/130ece19ac0dc7572f274f8ea4073618d07abada
Are you now able to proceed?
Does that mean that there is some automation by CI that updated the rest of the module artifacts?
Am not aware of that. I had to manually update the module versions as i stated above.
@samuel34 are you doing any special modifications to the CI plan before releasing? https://ci.openmrs.org/browse/TRUNK-TWOONEX-84
Am asking this because your releases from CI (for the second time now) always result into a release version branch instead of tag. For instance, when you released 2.0.7, a branch named 2.0.7 was created instead of the 2.07 tag. Today when you released 2.1.4, a branch named 2.1.4 was created instead of the 2.1.4 tag.
I always end up deleting these branches and release again from CI.