Looking for the OpenMRS 2.6.0 Platform Release Manager

Yes… I don’t think there’s a secure way to allow this to be done through Bamboo. I’ve reapplied the fix for this. PS, we need to be a little careful with these jobs. The 2.6.x branch was publishing dev images called 2.5.x-dev…

Rebuild currently on-going here.

Thanks to the discussions during the platform call today and the efforts of @burke @ibacher @dkayiwa @abertnamanya and @jwnasambu , we have a passing build at #61.

We can now go ahead and deploy platform 2.6.0-alpha to the UAT Platform Server.

2 Likes

I think we are ready for the prerelease(alpha). However, we have one question. Do we need to go through the steps from 15 to 17 under the steps to follow for all releases section for the alpha release? @dkayiwa

cc: @abertnamanya @jwnasambu

IMO Since OpenMRS_Platform_2.6.0-alpha is already out, all you wanna do is set a timeline for it, invite testers for the features you released from the community, including yourself. using your UAT server.

and update the RoadMap for 2.6.0 Issues,(I can see the wiki for alpha is done good Job !)

After that is done, collect anything missing and prepare beta, if there are no more issues, and if all is well , then prepare for 2.6.0

1 Like

Thanks @tendomart , quick question though. How do we test using the UAT Server. Could you point me to a resource or two?

more clarity here too!

Did you deploy it anywhere? of you just went ahead with release.

There is this https://uat-platform.openmrs.org/openmrs/owa/addonmanager/index.html#/login

But the best option would be to have Refapp 2.12.0 run on top of 2.6.0-alpha, though not mandatory

You can use Refapp 2.12.0 run on alpha 2.6.0 if not testing platform directly, for all or some of the features at the alpha 2.6.0 wiki https://uat-refapp.openmrs.org/openmrs/login.htm

Deployed it on UAT Platform Server.

I think this would make testing abit easy

Yeah it would.

i have gone through a couple of resources on UAT Platform and none seems to really describe how testing of platform can be done on the UAT Platform Server.

Any help rendered to me in that regard is highly welcome @tendomart @kdaud

@mherman22 Nothing really hard, the Idea is look at the Tickets done at your Release notes page, those are things you need to test, using the Refapp.

Some are deployment Issues and may require a local setup or a remote setup to test the container state instance it’s self like [TRUNK-6083] Build and deploy docker image for openmrs-core - OpenMRS Issues, for such an issue, you can pull the image and spin a container on your local machine or still setup the container on one of the remote servers on the openmrs infra.

2 Likes

This server is running platform 2.6.0-alpha: qa-refapp.openmrs.org

It would be enough if some rudimentary testing is done to ensure that all the features here: Reference Application 2.11.0 - Documentation - OpenMRS Wiki, work as advertised.

3 Likes

Thanks @tendomart , this is really helpful.

Great. I will share the talkpost for everyone to test out the 2.6.0-alpha and I’ll take part too in the process.

Thanks @dkayiwa

I think it’s about time we moved ahead and began on the beta release since the time set for the alpha release testing is done..

Was any testing done? If yes, how did it go? What were the results?

Tested against the https://qa-refapp.openmrs.org/openmrs/referenceapplication/home.page using the qaframework feature workflows. I did this locally.

checkoout → OpenMRS Platform 2.6.0-alpha Testing - Google Sheets for the results.

And i think everything looks okay unless i missed something.

Then your suggestion of moving to beta makes sense. :slight_smile:

1 Like

We are getting the following when we try to release core 2.6.0-beta to maven.

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project openmrs: Failed to deploy artifacts: Could not find artifact org.openmrs:openmrs:pom:2.6.0-beta in openmrs-repo-releases (https://mavenrepo.openmrs.org/nexus/content/repositories/releases) -> [Help 1]

/cc: @abertnamanya @dkayiwa @tendomart

@mherman22 did which release number did you use, it’s complaining 2.6.0-beta

*[ERROR] mvn release:perform failed. Fix the problem and try another release number.*

I deleted the tag 2.6.0-beta and release again.

And did you make the version 2.6.0-beta-SNAPSHOT

Thanks for deleting the tag. i am gonna release again.

Yes and Here are the custom variables i used

maven.release.version|2.6.0-beta|
maven.development.version|2.6.0-beta-SNAPSHOT

/cc: @tendomart