As mentioned in the other talk post,[quote=“jdegraft, post:1, topic:6144”]
Reference Application 2.4 release issue
[/quote] should not be an issue.
Also, you should setup UAT with unreleased versions for the 4 modules you mentioned. If any issues are identified in UAT, they need to be handled before releasing the 4 modules (as releasing the 4 modules will make 2.4 released).
The pull request can be merged while UAT is ongoing.
Correct. I have included them in the list by mistake.
Releasing coreapps sounds good.
In case of Ref App 2.4 to UAT, I Just want you to make sure referencemetadata, referencedemodata, and referenceapplication are not released as it might create issues with version numbering and we might have to release 2.4.1 at the time of final release. Otherwise, it sounds good to me.
@jdegraft, Thank you for leading us through the release process. I know it involved a lot of your hard work and effort in dealing with the issues that came up during the release process.
Ah. Looks like the same problem I’m seeing: unable to SSH into that VM.
@dkayiwa, @jdegraft – please confirm that a help desk ticket has been created, they understand the priority, and check in on status daily. Thanks! If you have not heard anything from the help desk within 24 hours, then please let us know here.
@jdegraft, please reply to that help desk ticket (CC’ing myself & @dkayiwa) stating this is a blocker for Reference Application 2.4 release, any help on restoring SSH access to uat02 would be appreciated (including completely resetting the VM). If the help desk is blocked – i.e., they are stuck waiting on the VM host to take action – then we can ask them to elevate that ticket and, in the meantime, look elsewhere for a temporary solution (e.g., I could pay for a digital ocean VM and have the help desk point uat-refapp.openmrs.org to it until uat02 can be fixed).
Hey there all – please keep in mind that the help desk is not paid and are entirely volunteer – so please keep in that in mind and set your expectations accordingly. You won’t get immediate action – sorry about that. Beyond this, I do not know. According to a document I found, I don’t know if resources have been assigned for uat02. This link requires that you use your OpenMRS email address.
@burke, to be explicit, assuming that the helpdesk assignments article we’re referring to is up-to-date, uat01.openmrs.org (GW152) should be free to commandeer, and we don’t need to touch devtest00 or devtest04 (for this purpose).
I’m just going to be explicit – a large chunk of the infra team is going to be in Austin for OSCON, and I believe @ryan is away. @maany is busy and perhaps recovering from exams. So unless a server goes down, ro something like that, this is going to have to wait. Sorry. If you want this to not fall through the cracks, ping one of the open cases for this issue.