An overview of the forthcoming next release for REF-APP 2.11.0

[ssmusoke (Stephen Senkomago Musoke)]

@prapakaran Can you create a new server using OpenMRS SDK, the distribution to select is Reference Application 2.11.0-SNAPSHOT

[sharif (Sharif Magembe)]

@ssmusoke

Many will grimace at the thought but IMO, 2-4 are modules with specific workflows that build on the Ref App distribution (there is no much additional automation that is needed).

Obviously Ref App distro project may need to be moved in favor of module based referencing with openmrs-distro.properties

cc @ssmusoke @akanter we did not finish this conversation about covid-19 metadata concepts inclusion in ref-app. what could be your final conclusion on this matter

[burke (Burke Mamlin)]

@mogoodrich

@mogoodrich

if the Ref App is targeting Core 2.4.0, I would probably hold off doing module releases until the Core/Platform 2.4.0 is stable and released?

That’s definitely true thanks @mogoodrich .we are still in reviewing tickets, looking for bugs in different core modules, bythe time platform is to be released, we will have gone miles of stablizing modules to be released

@sharif & @mogoodrich, I would target Platform 2.3 for this Ref App 2.11 release. We are hoping to get Platform out this fall, but making it a dependency for Ref App 2.11 would push this release back close to when we’d expect Ref App 2.12 in Spring 2021.

I’d recommend we refresh modules and try to include the OpenMRS SPA module for Ref App 2.11. Hopefully, this will allow us to get it released closer to the expected target of October 2020.

[sharif (Sharif Magembe)]

@burke

I would target Platform 2.3 for this Ref App 2.11 release. We are hoping to get Platform out this fall, but making it a dependency for Ref App 2.11 would push this release back close to when we’d expect Ref App 2.12 in Spring 2021.

Thanks @burke for that clarification

@burke

ry to include the OpenMRS SPA module for Ref App 2.11.

i think i will definitely try to work on this, May be if there are other improvements that need to be worked on before we bundle it in Ref-App

@burke

Hopefully, this will allow us to get it released closer to the expected target of October 2020.

Does this mean we target to the release in october or we still maintain the full release in january 2021

[mogoodrich (Mark Goodrich)]

I think the consensus is we target an October 2020 release, based on Core 2.3.x, and with mainly a module refresh…

[mozzy (Moses Mutesasira)]

@mogoodrich

October 2020 release,

Mainly i think it will depend on the status of the SPA module.

could we have an MVP of the SPA module by october /2020 ?? cc @bistenes @mksd @ibacher

[sharif (Sharif Magembe)]

@mozzy

could we have an MVP of the SPA module by october /2020

Nice catch @mozzy actually i wanted to bring this in the TAC call but thanks for bringing this up

[mozzy (Moses Mutesasira)]

@burke

I would target Platform 2.3 for this Ref App 2.11 release.

From the comments here , we agreed to keep the platform at 2.3 for this release ,

but am seeing it updated to 2.4.0-SNAPSHOT here … can we revert that ?? cc @sharif

[jwnasambu (Juliet Wamalwa)]

+1 consent . I can’t Imagine the whole year without a release!

[sharif (Sharif Magembe)]

@mozzy

but am seeing it updated to 2.4.0-SNAPSHOT here … can we revert that ??

Thanks @mozzy for that catch , created a ticket here, can you make it ready for work

[mozzy (Moses Mutesasira)]

@sharif

can you make it ready for work

cool. done

[sharif (Sharif Magembe)]

@mozzy

cool. done

Thanks @mozzy finished that PR

[tendomart (tendo kiiza Martyn)]

@sharif

Thanks @mozzy finished that PR

@sharif don’t you think the module Snapshot versions need reverting as well ?

[sharif (Sharif Magembe)]

@tendomart

don’t you think the module Snapshot versions need reverting as well ?

@tendomart i think those module versions are already set not until there is confirmation from module owners or module maintainers of which version that we are going to go with in Next Ref-App 2.11.0. then we can continue and update them later That change of openmrsVersion was because we tended to continue depend on 2.3.0 platform, we expect to have many changes from snapshots to stable versions to be released

However @tendomart thanks again, Am going to create a thread reminding on different module owners and maintainers of these versions such that they be aware or May be they can let us know of any information of such modules

[mozzy (Moses Mutesasira)]

Hey all , It seems weve got some regression,

since we reverted the platform 2.4.0-SNAPSHOT to 2.3.1 in the reff app distribution , the standalone build failed at https://ci.openmrs.org/browse/REFAPP-OMODDISTRO-TS-10273/log .

Tried to look through the failure and discovered ,there was some changes and upgrade introduced into the standalone project for reff app here that were incompatible with the liquibase version in core 2.3.1 .

Note that starting at Liquibase 3.7.0 , there are some backward Incompantible API changes.

so i have again reverted back to platform 2.4.0-SNAPSHOT because we have liquibase upgraded

.Other possible work arounds

• upgrade the liquibase version in core 2.3.2-SNAPHOT ,and we have a minor release of platform 2.3.2 , and then depend on that.
• We revert this change in a separte branch ie (openmrs-emr2_for_2.3.x) to have a standalone branch ,thats still compatiple with platform 2.3.x as it is

cc @sharif @grace @dkayiwa @ibacher @jennifer @gcliff

[sharif (Sharif Magembe)]

Thanks @mozzy for that catch , i think that’s why other releases have been failing with distro because it seems the error is the same .

@mozzy

so i have again reverted back to platform 2.4.0-SNAPSHOT because we have liquibase upgraded

@mozzy does it fail again when you revert it back to 2.4.0-SNAPSHOT, havent seen the log reminder

[mozzy (Moses Mutesasira)]

@sharif

i think that’s why other releases have been failing with distro because it seems the error is the same .

what do you mean other releases ??

@sharif

does it fail again when you revert it back to 2.4.0-SNAPSHOT,

The standalone Build succeds on platform 2.4.0-SNAPSHOT.

Just that UI tests fail because qa-server is down . havent looked into why qa-server failed to start

[sharif (Sharif Magembe)]

@mozzy

what do you mean other releases ??

Thanks to @mogoodrich, have been releasing these module and i have been seeing ref-app distro failing, i dont know if you saw it

[gcliff (CLIFF GITA)]

@mozzy

upgrade the liquibase version in core 2.3.2-SNAPHOT ,and we have a minor release of platform 2.3.2 , and then depend on that.

thanks @mozzy for bringing this up

i vouch for the first work around option

[sharif (Sharif Magembe)]

@gcliff

i vouch for the first work around option

Thanks @gcliff, could let us know when this change is ready, , to resume working on RA-1818 back to 2.3. hope you are going to create those tickets unless otherwise