# Platform 2.3 Beta Release

**URL:** <https://talk.openmrs.org/t/platform-2-3-beta-release/24458>\
**Category:** Development\
**Created:** [August 24, 2019, 2:54am UTC](https://talk.openmrs.org/t/platform-2-3-beta-release/24458 "2019-08-24T02:54:48Z")\
**Posts on this page:** 14\
**Page:** 1

<div class="post-metadata">

**Author:** ![c.antwi](https://talk.openmrs.org/user_avatar/talk.openmrs.org/c.antwi/32/7911_2.png) [@c.antwi](https://talk.openmrs.org/u/c.antwi)\
**Post date:** [August 24, 2019, 2:54am UTC](https://talk.openmrs.org/t/platform-2-3-beta-release/24458/1 "2019-08-24T02:54:48Z")

</div>

Hi @ruhanga were you able to complete the remaining work for plat 30? Are you facing any blockers?

Can you also please update your release page [https://wiki.openmrs.org/display/RES/Platform+2.3.0+Release+Management+Page](https://wiki.openmrs.org/display/RES/Platform+2.3.0+Release+Management+Page) to reflect the current status of tickets 🙂

---

<div class="post-metadata">

**Author:** ![ruhanga](https://talk.openmrs.org/user_avatar/talk.openmrs.org/ruhanga/32/8318_2.png) [@ruhanga](https://talk.openmrs.org/u/ruhanga)\
**Post date:** [August 25, 2019, 8:18am UTC](https://talk.openmrs.org/t/platform-2-3-beta-release/24458/2 "2019-08-25T08:18:17Z")

</div>

Hi @c.antwi, thanks for the kind reminder. In a nut shell, all work on PLAT-30 is ready for merging. Towards the end of this past week I’ve had unexpectedly an emergency of a patient to care-take which interrupted my routines. Kind apologies, our Platform 2.3.Beta should have been released by the 23rd this month. I’m having to catch up ASAP to ensure we have this released out by 26th. I’ll be updating the release management page accordingly. Otherwise I currently do not have any blocker.

---

<div class="post-metadata">

**Author:** ![ruhanga](https://talk.openmrs.org/user_avatar/talk.openmrs.org/ruhanga/32/8318_2.png) [@ruhanga](https://talk.openmrs.org/u/ruhanga)\
**Post date:** [August 30, 2019, 4:17pm UTC](https://talk.openmrs.org/t/platform-2-3-beta-release/24458/3 "2019-08-30T16:17:04Z")

</div>

Hi all,

I’d like to have the released downloadable Platform version which at the moment is 2.3.0-alpha built on Bamboo to Sourceforge. Is there any extra credential or config that is necessary for this? Artifacts except the SNAPSHOT version that failed were released to Maven. This can be seen here [https://ci.openmrs.org/browse/OP-OPM7-4/log](https://ci.openmrs.org/browse/OP-OPM7-4/log) . Bamboo was not smart enough to figure out the correct SNAPSHOT.

What could be the way forward to have the artifacts published to Sourceforge? Thanks.

cc: @cintiadr, @samuel34, @dkayiwa

---

<div class="post-metadata">

**Author:** ![cintiadr](https://talk.openmrs.org/user_avatar/talk.openmrs.org/cintiadr/32/8081_2.png) [@cintiadr](https://talk.openmrs.org/u/cintiadr)\
**Post date:** [August 31, 2019, 8:44am UTC](https://talk.openmrs.org/t/platform-2-3-beta-release/24458/4 "2019-08-31T08:44:00Z")

</div>

So the release step failed for a very weird reason.

It was able to successfully

```auto
|build|30-Aug-2019 06:55:02|[INFO] Cleaning up after release...|
|---|---|---|
|build|30-Aug-2019 06:55:02|[INFO] ------------------------------------------------------------------------|
|build|30-Aug-2019 06:55:02|[INFO] BUILD SUCCESS|
|build|30-Aug-2019 06:55:02|[INFO] ------------------------------------------------------------------------|
|build|30-Aug-2019 06:55:02|[INFO] Total time: 59.325 s|
|build|30-Aug-2019 06:55:02|[INFO] Finished at: 2019-08-30T06:55:02+00:00|
|build|30-Aug-2019 06:55:02|[INFO] Final Memory: 12M/174M|
|build|30-Aug-2019 06:55:02|[INFO] ------------------------------------------------------------------------|

```

And from the [code](https://github.com/openmrs/openmrs-contrib-bamboo/blob/master/release-prepare-perform.sh#L109), you can see it started the snapshot deployment.

`mvn deploy -DskipTests -B`

And then I went to the distribution [code](https://github.com/openmrs/openmrs-distro-platform/blob/master/pom.xml#L90), and it’s calling `build-distro` on the `process-resources` phase by default. So it makes sense that maven is attempting to download the snapshot (as the war would be only created after the `package` maven phase.

So I’d probably recommend to bind `build-distro` to [phase later](https://www.tutorialspoint.com/maven/maven_build_life_cycle.htm) than `package`. You can test that by deleting the snapshots from your `~/.m2/repository` folder, and running `mvn install`, and verify that the `build-distro` phase didn’t attempt to download a snapshot.

---

<div class="post-metadata">

**Author:** ![cintiadr](https://talk.openmrs.org/user_avatar/talk.openmrs.org/cintiadr/32/8081_2.png) [@cintiadr](https://talk.openmrs.org/u/cintiadr)\
**Post date:** [August 31, 2019, 8:44am UTC](https://talk.openmrs.org/t/platform-2-3-beta-release/24458/5 "2019-08-31T08:44:24Z")

</div>

After you do that, I recommend you cut another release, possibly `alpha-2` or similar.

No shortage of numbers 🙂

---

<div class="post-metadata">

**Author:** ![herbert24](https://talk.openmrs.org/user_avatar/talk.openmrs.org/herbert24/32/8178_2.png) [@herbert24](https://talk.openmrs.org/u/herbert24)\
**Post date:** [September 2, 2019, 7:42am UTC](https://talk.openmrs.org/t/platform-2-3-beta-release/24458/6 "2019-09-02T07:42:04Z")

</div>

cc ruhanga

---

<div class="post-metadata">

**Author:** ![c.antwi](https://talk.openmrs.org/user_avatar/talk.openmrs.org/c.antwi/32/7911_2.png) [@c.antwi](https://talk.openmrs.org/u/c.antwi)\
**Post date:** [September 11, 2019, 2:14pm UTC](https://talk.openmrs.org/t/platform-2-3-beta-release/24458/7 "2019-09-11T14:14:28Z")

</div>

@ruhanga How far are we? Can we get this piece of work finished this week?

---

<div class="post-metadata">

**Author:** ![ruhanga](https://talk.openmrs.org/user_avatar/talk.openmrs.org/ruhanga/32/8318_2.png) [@ruhanga](https://talk.openmrs.org/u/ruhanga)\
**Post date:** [September 11, 2019, 8:42pm UTC](https://talk.openmrs.org/t/platform-2-3-beta-release/24458/8 "2019-09-11T20:42:42Z")

</div>

Hi @c.antwi, I’m doing a number of testing and so far a few bugs may need to be fixed before a beta release. Gathering a few more details. I’ll be opening talk threads for those so far found. In brief,

1. The latest OpenMRS Concept dictionary is a little out of sync with the Platform, atleast with the version I’ve tested with (openmrs\_concepts\_2.2). Updating the database onto of the this specified version of the Concept Dictionary produces [a liquibase update error](https://pastebin.com/xFj3wCPw).
2. A minor bug uncovered by the work done on Alternate Authentication schemes, doing a logout of the platform after triggering the platform’s context refresh then doing a login again fails until one clears the browser cache. I’ve reported this issue on the related ticket [TRUNK-381](https://issues.openmrs.org/browse/TRUNK-381). Some work is already being done towards resolving this, first to get the exact culprit.

---

<div class="post-metadata">

**Author:** ![wyclif](https://talk.openmrs.org/user_avatar/talk.openmrs.org/wyclif/32/19607_2.png) [@wyclif](https://talk.openmrs.org/u/wyclif)\
**Post date:** [September 22, 2019, 1:11am UTC](https://talk.openmrs.org/t/platform-2-3-beta-release/24458/9 "2019-09-22T01:11:04Z")

</div>

Is the beta release out?

We wanted to annotate more classes in core that represent patient clinical data i.e Allergy, Diagnosis and Condition and include this in 2.3 release, I can possibly get this done by end of Tuesday .

---

<div class="post-metadata">

**Author:** ![wyclif](https://talk.openmrs.org/user_avatar/talk.openmrs.org/wyclif/32/19607_2.png) [@wyclif](https://talk.openmrs.org/u/wyclif)\
**Post date:** [September 29, 2019, 7:06pm UTC](https://talk.openmrs.org/t/platform-2-3-beta-release/24458/10 "2019-09-29T19:06:10Z")

</div>

I have created [TRUNK-5660](https://issues.openmrs.org/browse/TRUNK-5660), [TRUNK-5661](https://issues.openmrs.org/browse/TRUNK-5661) and [TRUNK-5662](https://issues.openmrs.org/browse/TRUNK-5662) to use annotations for Allergy, Condition and Diagnosis

---

<div class="post-metadata">

**Author:** ![ruhanga](https://talk.openmrs.org/user_avatar/talk.openmrs.org/ruhanga/32/8318_2.png) [@ruhanga](https://talk.openmrs.org/u/ruhanga)\
**Post date:** [September 30, 2019, 8:13am UTC](https://talk.openmrs.org/t/platform-2-3-beta-release/24458/11 "2019-09-30T08:13:54Z")

</div>

Hi @wyclif, sorry I lost track of your prior comment. The platform 2.3.0-beta was release about a week ago packaged with the featured tickets [here](https://wiki.openmrs.org/display/RES/Platform+2.3.0+Release+Management+Page). Here is the related topic [OpenMRS Platform 2.3.0-beta released for testing](https://talk.openmrs.org/t/openmrs-platform-2-3-0-beta-released-for-testing/24795).

We will most probably backport these changes when merged into master to the associated branch 2.3.x as part of its maintenance releases once 2.3.0 full release is out as well.

---

<div class="post-metadata">

**Author:** ![wyclif](https://talk.openmrs.org/user_avatar/talk.openmrs.org/wyclif/32/19607_2.png) [@wyclif](https://talk.openmrs.org/u/wyclif)\
**Post date:** [October 1, 2019, 4:36am UTC](https://talk.openmrs.org/t/platform-2-3-beta-release/24458/12 "2019-10-01T04:36:31Z")

</div>

Ok, thanks!

---

<div class="post-metadata">

**Author:** ![wyclif](https://talk.openmrs.org/user_avatar/talk.openmrs.org/wyclif/32/19607_2.png) [@wyclif](https://talk.openmrs.org/u/wyclif)\
**Post date:** [October 1, 2019, 4:37am UTC](https://talk.openmrs.org/t/platform-2-3-beta-release/24458/13 "2019-10-01T04:37:43Z")

</div>

@ruhanga we actually want to backport them before the release so that they are in the 2.3.0 version

---

<div class="post-metadata">

**Author:** ![ruhanga](https://talk.openmrs.org/user_avatar/talk.openmrs.org/ruhanga/32/8318_2.png) [@ruhanga](https://talk.openmrs.org/u/ruhanga)\
**Post date:** [October 2, 2019, 6:28am UTC](https://talk.openmrs.org/t/platform-2-3-beta-release/24458/14 "2019-10-02T06:28:42Z")

</div>

Thank you @wyclif, hoping this goes through well. Let me know as soon as the above tickets are merged into master as I’m getting the full release out in the next one week if we have no issues reported to address with the 2.3.0-beta release.

cc @mogoodrich, @c.antwi, @mksd, @dkayiwa
