OpenMRS 2.3.4 release

Development
,
1

Hi all -

I’d like to release OpenMRS 2.3.4 from the 2.3.x branch. Is there any opposition to this? Can someone in the know please point me to the steps I need to follow? Is it just a matter of going into Bamboo and clicking the “Release” button here: OpenMRS Platform - Openmrs Platform 2.3.x 106: Build result summary - OpenMRS Bamboo and ensuring JIRA is up-to-date?

Thanks, Mike

2

You need to basically provide

  1. Create a 2.3.4 Tag as the release version

  2. Provide the development version of that Branch as a snapshot

This should release core to maven . And i believe you repeat the steps so platform may be packaged for you .

Does that help in way ?

3

All good on our end! Thanks @mseaton!

4

First you need to actually release the 2.3.4 version of core here. Then you should be able to release the actual platform… though I never quite got that part working with 2.4.1…

5

Thanks @ibacher . That was helpful. OpenMRS core 2.3.4 has been released. You can find the war file here .

Is there documentation of any next steps that I need to do beyond this? For my purposes the war file is sufficient, as that is what distributions depend on and pull in as a dependency. Is the process for releasing a platform version from this release version straightforward? Is it documented? Is it necessary?

Thanks, Mike

6

We have a pretty detailed Wiki page.

7

Thanks @ibacher - I had found that, but I was hoping someone would tell me - you don’t need to do 99% of that if you just want to release a new maintenance artifact of a branch. There is a lot there. I think we need to distinguish the nice-to-haves from the essentials.

8

Agreed with @mseaton here, we need to make Core patch releases as easy and lightweight as can be.

9

So, I started this talk thread, released openmrs 2.3.4 (api, web, war), released the 2.3.4 version in JIRA, created a new 2.3.5 version in JIRA, and initiated the Platform 2.3.4 job in Bamboo, which made it up until the “Release Standalone” stage at which point it failed.

I didn’t do any of the steps related to downloading and updating CIEL and I didn’t do anything related to the UAT environment, with Sourceforge, with all of those helpdesk steps, with blog posting, etc.

As far as the error that happened during the Platform release, this is what I see in the Bamboo log:

07-Dec-2021 22:15:09	[INFO] ------------------------------------------------------------------------
07-Dec-2021 22:15:09	[INFO] Reactor Summary:
07-Dec-2021 22:15:09	[INFO] 
07-Dec-2021 22:15:09	[INFO] standalone ......................................... SUCCESS [ 30.394 s]
07-Dec-2021 22:15:09	[INFO] standalone-step-01 ................................. SUCCESS [02:40 min]
07-Dec-2021 22:15:09	[INFO] standalone-step-02 ................................. SUCCESS [01:20 min]
07-Dec-2021 22:15:09	[INFO] standalone-step-03 ................................. FAILURE [11:11 min]
07-Dec-2021 22:15:09	[INFO] standalone-step-04 ................................. SKIPPED
07-Dec-2021 22:15:09	[INFO] standalone-step-05 ................................. SKIPPED
07-Dec-2021 22:15:09	[INFO] ------------------------------------------------------------------------
07-Dec-2021 22:15:09	[INFO] BUILD FAILURE
07-Dec-2021 22:15:09	[INFO] ------------------------------------------------------------------------
07-Dec-2021 22:15:09	[INFO] Total time: 15:43 min
07-Dec-2021 22:15:09	[INFO] Finished at: 2021-12-07T22:15:09+00:00
07-Dec-2021 22:15:10	[INFO] Final Memory: 116M/1452M
07-Dec-2021 22:15:10	[INFO] ------------------------------------------------------------------------
07-Dec-2021 22:15:10	[ERROR] Failed to execute goal org.liquibase:liquibase-maven-plugin:4.4.1:update (empty-db-update-to-latest) on project standalone-03: Execution empty-db-update-to-latest of goal org.liquibase:liquibase-maven-plugin:4.4.1:update failed: An API incompatibility was encountered while executing org.liquibase:liquibase-maven-plugin:4.4.1:update: java.lang.NoSuchMethodError: liquibase.database.Database.getTypeName()Ljava/lang/String;

@ibacher / @burke / @dkayiwa / @mksd - is the value of producing the standalone up for debate?

As @mksd said, the red tape is too high for a patch release of a maintenance branch. I’m happy to work through the necessary, but I’d love to confirm what is actually necessary before I embark on it.

Mike

10

Personally, I don’t think the value of a patch standalone (at least of the platform) is worth it.