Proposal for Limited Scope RefApp 2.13 & request for Release Manager

,

I wouldn’t mind running the server and share the screenshot.

When i look at OpenMRS - Home, it does not reflect 2.6.0 and this pull request is also not changing it from 2.6.0 fixed the distro.platform file with the 2.5.8 required info by jwnasambu · Pull Request #63 · openmrs/openmrs-contrib-ansible-docker-compose · GitHub

Its unfortunate I don’t have access to the mdsbuilder server so I can’t go beyond the login page. Besides, if you don’t mind let me share the screenshot of my local server shortly.

Just look at the bottom of the login page for the OpenMRS platform version that it is running.

At the bottom it shows 2.4.2 version. Kindly don’t get tired of my many questions. I desire to understand and learn from every process so as help someone else in future.

If i were tired, i would not be responding to you by now. :smiley:

1 Like

:rofl: :rofl: :rofl: :rofl: :rofl: :rofl: :rofl: This is a nice one.

Its unfortunate I was making my conclusion basing the highlighted part on the screenshot below

Which code did you run to have that?

Well, I may not answer you directly but on the release process steps: 1 I simply created a Reference Application 2.13.0 instance to ensure the server runs on the platform version on which the Reference Application distro version will be released on(After releasing the modules to the new version)

The versions of refapp 2.13.0 are supposed to be set from here: openmrs-distro-referenceapplication/pom.xml at 2.x · openmrs/openmrs-distro-referenceapplication · GitHub

Actually I installed 2.13.0-SNAPSHOT version.

@ibacher thanks for the point out on the way forward on this. Let me try it out when am sober.

@ibacher the server is running on 2.4.2 but then I have to change the platform version to support the current release version. That is why I come with this PR Comparing master...update_distro_platform_version · openmrs/openmrs-contrib-ansible-docker-compose · GitHub. Am sorry my question could have not made sense at first.

You need to also update the versions here: openmrs-distro-referenceapplication/pom.xml at 2.x · openmrs/openmrs-distro-referenceapplication · GitHub

Thanks so much @dkayiwa

Ok… I’ve merged this PR.

Am sorry I have delayed pushing this changes. I was blocked I couldn’t push the changes on github but now I can tell where the problem was and very soon I will ping you to review the PR.

Kindly I have failed to push the changes on this repo

When I push the changes, this is warning I get on my terminal

$ git push Username for 'https://github.com': jwnasambu remote: Support for password authentication was removed on August 13, 2021. remote: Please see https://docs.github.com/en/get-started/getting-started-with-git/about-remote-repositories#cloning-with-https-urls for information on currently recommended modes of authentication. fatal: Authentication failed for 'https://github.com/openmrs/openmrs-distro-referenceapplication.git/'

Its the same error I have been troubling with since yesterday and followed this guide to troubleshoot the problem but still getting the same error. When I run git log, I see my branch listed in the history and not visible on my forked repo on github. Kindly how can I go about it

Did you try this? Creating a personal access token - GitHub Docs