# OpenMRS Platform 2.3.0-beta released for testing **URL:** \ **Category:** Platform\ **Tags:** releases\ **Created:** [September 20, 2019, 1:47pm UTC](https://talk.openmrs.org/t/openmrs-platform-2-3-0-beta-released-for-testing/24795 "2019-09-20T13:47:19Z")\ **Posts on this page:** 8\ **Page:** 6
**Author:** ![mozzy](https://talk.openmrs.org/user_avatar/talk.openmrs.org/mozzy/32/11815_2.png) [@mozzy](https://talk.openmrs.org/u/mozzy)\ **Post date:** [January 24, 2020, 8:55am UTC](https://talk.openmrs.org/t/openmrs-platform-2-3-0-beta-released-for-testing/24795/101 "2020-01-24T08:55:12Z")
@ruhanga , a momment before that , from this talk thread here > [@Bamboo Build Failure Due to Platform Upgrade](https://talk.openmrs.org/t/bamboo-build-failure-due-to-platform-upgrade/26339/29): > > @mozzy have you tested to confirm that a new platform install has an admin account with a username, when you do not have that commit? we are coming to a resolution of reverting this commit here > see talk discussion that led to that commit here > [@Admin user doesn't have a username.](https://talk.openmrs.org/t/admin-user-doesnt-have-a-username/25145): > > Hello People, We are working on [enabling bahmni appointments to run on OpenMRS](https://talk.openmrs.org/t/running-bahmni-appointments-scheduling-on-openmrs/24935). This application leverages logged-in user’s username. It sets the current logged-in username in the cookies and uses it later. This works for all the users but the admin user. We see that admin user doesn’t have a username and the cookie is set to null. We checked out on [bahmni-demo](https://demo.mybahmni.org/openmrs) and found out that the username for admin is populated but not on [OpenMRS Demo](https://demo.openmrs.org). Any specific reason why the admin user doesn’t have a… , So it may need reverting and also some testing but please first follow the discusion [above](https://talk.openmrs.org/t/bamboo-build-failure-due-to-platform-upgrade/26339/6) for more insight ---
**Author:** ![mogoodrich](https://talk.openmrs.org/user_avatar/talk.openmrs.org/mogoodrich/32/3324_2.png) [@mogoodrich](https://talk.openmrs.org/u/mogoodrich)\ **Post date:** [January 24, 2020, 2:01pm UTC](https://talk.openmrs.org/t/openmrs-platform-2-3-0-beta-released-for-testing/24795/102 "2020-01-24T14:01:02Z")
> [@dkayiwa](#): > > I had thought that a switch to annotations would be obvious. But it turned out not to be so, basing on the side effects that we have experienced, and probably more would show up. Therefore, instead of annotations delaying the 2.3.0 release, i would bump them to 2.4.0 or even 3.0.0 I agree with this… annotations are certainly the more “modern” way for doing things so we should seriously consider upgrading, but we should do it at a point when we are confident to have the resources for a details regression test, and a strategy for avoiding things like the “unused\_tables”. Take care, Mark ---
**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:** [January 24, 2020, 2:23pm UTC](https://talk.openmrs.org/t/openmrs-platform-2-3-0-beta-released-for-testing/24795/103 "2020-01-24T14:23:54Z")
> [@mozzy](#): > > coming to a resolution of reverting this commit here > > [github.com/openmrs/openmrs-core](https://github.com/openmrs/openmrs-core/commit/34a42ea53643c4aa23ab9e78c1c398a3a1b11c8f) > > [![mddubey](https://avatars3.githubusercontent.com/u/5915340?v=4) ](https://github.com/mddubey) > > #### [TRUNK-5672: Add liquibase changeset to populate username for admin user (#3034)](https://github.com/openmrs/openmrs-core/commit/34a42ea53643c4aa23ab9e78c1c398a3a1b11c8f) > > by [mddubey](https://github.com/mddubey) on [08:23PM - 23 Oct 19 UTC](https://github.com/openmrs/openmrs-core/commit/34a42ea53643c4aa23ab9e78c1c398a3a1b11c8f) > > changed **1 files** with **12 additions** and **0 deletions**. Thanks @mozzy for timely pointing this out, > [@mozzy](#): > > So it may need reverting and also some testing > > but please first follow the discusion [above](https://talk.openmrs.org/t/bamboo-build-failure-due-to-platform-upgrade/26339/6) for more insight I’ve gone through the thread you shared but unfortunately I’m running out of bandwidth. I hope to get all this tested after reverting locally before merging this though. ---
**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:** [January 26, 2020, 7:04pm UTC](https://talk.openmrs.org/t/openmrs-platform-2-3-0-beta-released-for-testing/24795/104 "2020-01-26T19:04:16Z")
What were the other issues? I thought we addressed them ---
**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:** [January 27, 2020, 12:46pm UTC](https://talk.openmrs.org/t/openmrs-platform-2-3-0-beta-released-for-testing/24795/105 "2020-01-27T12:46:39Z")
> [@mozzy](#): > > we are coming to a resolution of reverting this commit here > > [github.com/openmrs/openmrs-core](https://github.com/openmrs/openmrs-core/commit/34a42ea53643c4aa23ab9e78c1c398a3a1b11c8f) > > [![mddubey](https://avatars3.githubusercontent.com/u/5915340?v=4) ](https://github.com/mddubey) > > #### [TRUNK-5672: Add liquibase changeset to populate username for admin user (#3034)](https://github.com/openmrs/openmrs-core/commit/34a42ea53643c4aa23ab9e78c1c398a3a1b11c8f) > > by [mddubey](https://github.com/mddubey) on [08:23PM - 23 Oct 19 UTC](https://github.com/openmrs/openmrs-core/commit/34a42ea53643c4aa23ab9e78c1c398a3a1b11c8f) > > changed **1 files** with **12 additions** and **0 deletions**. @wyclif, the above revert issue is annotations unrelated. @mozzy, I’ve been doing a couple of tests, and reverting this is effective when using the SDK. By this I mean, installing a fresh instance of the platform with the current version of the SDK adds the **admin** user name to the _admin_ systemID as was fixed. However this is not the case when running on an enterprise tomcat server. I would think the later is not a big issue. ---
**Author:** ![mozzy](https://talk.openmrs.org/user_avatar/talk.openmrs.org/mozzy/32/11815_2.png) [@mozzy](https://talk.openmrs.org/u/mozzy)\ **Post date:** [January 27, 2020, 12:49pm UTC](https://talk.openmrs.org/t/openmrs-platform-2-3-0-beta-released-for-testing/24795/106 "2020-01-27T12:49:46Z")
> [@ruhanga](#): > > However this is not the case when running on an enterprise tomcat server. Have you done the tests, after reverting the commit ? ---
**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:** [January 27, 2020, 12:56pm UTC](https://talk.openmrs.org/t/openmrs-platform-2-3-0-beta-released-for-testing/24795/107 "2020-01-27T12:56:28Z")
Yes @mozzy. 🙂 ---
**Author:** ![mozzy](https://talk.openmrs.org/user_avatar/talk.openmrs.org/mozzy/32/11815_2.png) [@mozzy](https://talk.openmrs.org/u/mozzy)\ **Post date:** [January 27, 2020, 1:00pm UTC](https://talk.openmrs.org/t/openmrs-platform-2-3-0-beta-released-for-testing/24795/108 "2020-01-27T13:00:37Z")
> [@ruhanga](#): > > However this is not the case when running on an enterprise tomcat server. I would think the later is not a big issue. sure thats the expected behaviour. > [@ruhanga](#): > > adds the **admin** user name to the _admin_ systemID thats only possible when running with the latest SDK , Docker or the standalone , if am not mistaken. So i think ideally thats the expected behaviour cc @dkayiwa [Previous page](https://talk.openmrs.org/t/openmrs-platform-2-3-0-beta-released-for-testing/24795.md?page=5)