Looking for the OpenMRS Platform 2.8.0 Release Manager

Development
, , ,
1

Hi everyone,

We’re looking for a volunteer to serve as the Release Manager for the upcoming OpenMRS Platform 2.8.0 release, which is planned for July this year.

This is a great opportunity to contribute to the community and gain valuable experience. You’ll have the support of past release managers and community experts throughout the process.

To learn more about the release process and the responsibilities of a Release Manager, please check out the links below:

If you’re interested in taking on this role, please let us know. We’d love to have you onboard!

4 Likes
2

@wikumc we are going to release it next month (July).

1 Like
3

Oh, sorry about that :slight_smile: . I updated the post.

4

Hi @wikumc

I’m interested in volunteering as the Release Manager for the OpenMRS Platform 2.8.0 release scheduled for July.

I’d like to learn more about the specific responsibilities and timeline involved.

8 Likes
5

Hello, I’m available and interested in volunteering as a Co-Release Manager along with @suubi7 . I’d be glad to contribute and support the release process in any way I can.

5 Likes
6

Thank you @suubi7 and @sharif, for your interest! Since @suubi7 was the first to volunteer, I suggest he take the lead as the primary release manager. @sharif, if you’re still interested, you could collaborate with @suubi7 on the release process. It’s a great opportunity to gain some experience.

Hope you both are okay with that!

6 Likes
7

Good to me thanks @wikumc

2 Likes
8

Hi everyone,

Following up on my interest in the Release Manager role - I’m now working with @sharif on this initiative.

We have a call today to discuss the alpha version release and prioritize tickets that should be going in. Our goal is to have the alpha version release completed before the end of next week.

Will keep the community updated on our progress.

6 Likes
9

Hello @dkayiwa @wikumc @mherman22 @sharif I getting a unit test failure when trying to build

+ export IMAGE=openmrs/openmrs-core@sha256:80465ac463fe47edf1e05b56c24ee121ef8b0688c690a37806848093bffd19e8
+ IMAGE=openmrs/openmrs-core@sha256:80465ac463fe47edf1e05b56c24ee121ef8b0688c690a37806848093bffd19e8
+ docker pull openmrs/openmrs-core@sha256:80465ac463fe47edf1e05b56c24ee121ef8b0688c690a37806848093bffd19e8
+ docker run -v m2-repo:/root/.m2/repository --rm openmrs/openmrs-core@sha256:80465ac463fe47edf1e05b56c24ee121ef8b0688c690a37806848093bffd19e8 mvn test
[Field error in object 'term' on field 'conceptReferenceTermMaps[1].termB': rejected value [weight term(WGT234)]; codes [ConceptReferenceTerm.termToTerm.alreadyMapped.term.conceptReferenceTermMaps[1].termB,ConceptReferenceTerm.termToTerm.alreadyMapped.term.conceptReferenceTermMaps.termB,ConceptReferenceTerm.termToTerm.alreadyMapped.conceptReferenceTermMaps[1].termB,ConceptReferenceTerm.termToTerm.alreadyMapped.conceptReferenceTermMaps.termB,ConceptReferenceTerm.termToTerm.alreadyMapped.termB,ConceptReferenceTerm.termToTerm.alreadyMapped.org.openmrs.ConceptReferenceTerm,ConceptReferenceTerm.termToTerm.alreadyMapped]; arguments []; default message [Cannot map a reference term multiple times to the same concept reference term]]
[Fatal Error] :1:67: XML document structures must start and end within the same entity.
[Fatal Error] :-1:-1: Premature end of file.

The full build log is here.

10

That test fails randomly. I have not yet looked into why. But in the meantime, we can just try rebuilding, until it passes, such that you get going. Feel free to create a ticket for looking into this. But it should not block you.

3 Likes
11

@suubi7 , Did you file the ticket ?. i can look into it. Feel free to share it here.

12

Yes I did @sharif though after doing rebuilds it has stopped. here

13

@dkayiwa @wikumc @sharif am facing this issue here as am trying to release.

14

Has any of you just deleted the 2.8.0-alpha tag after you posted this? I am asking because i have just tried releasing and got fatal: tag '2.8.0-alpha' already exists but i checked and the tag does not exist.

15

Was wondering too, Am seeing it in the same error log. Hello @suubi7 .

16

Not that I know of @dkayiwa

17

@ruhanga we are planning to resume releasing standalone versions based on MariaDB, starting with platform 2.8.0-alpha. Since the standalone requires a minimum of Java 17 which is not yet supported by bamboo, are you able to help us, to at least, dockerise this build step for the standalone? Log in as a Bamboo user - OpenMRS Bamboo

1 Like
18

Certainly, happy to help with this.

2 Likes
19

@dkayiwa could this be the reason why the Release standalone job is failing?

1 Like
20

Caused by: java.lang.UnsupportedClassVersionError: ch/vorburger/mariadb4j/StartMojo has been compiled by a more recent version of the Java Runtime (class file version 61.0), this version of the Java Runtime only recognizes class file versions up to 52.0

Yes as you can see in the above log message on bamboo. You can disable the standalone stages for now.

1 Like