# Platform 2.2 Release is on 4th June 2018 **URL:** \ **Category:** Platform\ **Created:** [February 27, 2018, 1:07pm UTC](https://talk.openmrs.org/t/platform-2-2-release-is-on-4th-june-2018/16399 "2018-02-27T13:07:32Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![samuel34](https://talk.openmrs.org/user_avatar/talk.openmrs.org/samuel34/32/17813_2.png) [@samuel34](https://talk.openmrs.org/u/samuel34)\ **Post date:** [February 27, 2018, 1:07pm UTC](https://talk.openmrs.org/t/platform-2-2-release-is-on-4th-june-2018/16399/1 "2018-02-27T13:07:32Z")
Hi everyone, Am happy to announce to you that the target release date of **Platform 2.2** is on **4th June 2018**. We expect a lot of new features and a few bug fixes for this release as defined in the [Road Map](https://wiki.openmrs.org/display/docs/Technical+Road+Map) ##### The following are the new features expected in the Release - Change db setup to use liquibase ( [IDGEN-33](https://issues.openmrs.org/browse/IDGEN-33?src=confmacro) ) - Web-services for idgen ([IDGEN-42](https://issues.openmrs.org/browse/IDGEN-42?src=confmacro)) - Support for Encounter Diagnoses ([TRUNK-5015](https://issues.openmrs.org/browse/TRUNK-5015?src=confmacro)) - Support Provider Roles ([TRUNK-4791](https://issues.openmrs.org/browse/TRUNK-4791?src=confmacro)) - Added Creatable and Changeable interfaces ([TRUNK-4917](https://issues.openmrs.org/browse/TRUNK-4917?src=confmacro)) - Implementing Program Enrollment Attributes ([TRUNK-4755](https://issues.openmrs.org/browse/TRUNK-4755?src=confmacro)) - Bundle the Add-On manager OWA within the Platform ([PLAT-30](https://issues.openmrs.org/browse/PLAT-30?src=confmacro)) All that being said, I'm kindly making a call to anyone who feels there could be a missing new feature or bug fix that could be fixed or added prior to the release 2.2, feel free to give your thoughts/ideas Best Regards Platform 2.2 Release Manager Samuel Male Thanks! ---
**Author:** ![samuel34](https://talk.openmrs.org/user_avatar/talk.openmrs.org/samuel34/32/17813_2.png) [@samuel34](https://talk.openmrs.org/u/samuel34)\ **Post date:** [June 3, 2018, 10:42am UTC](https://talk.openmrs.org/t/platform-2-2-release-is-on-4th-june-2018/16399/3 "2018-06-03T10:42:17Z")
Hi, According to the scheduled release date, release must be due tomorrow(4th June). The tickets below have been successfully worked on and fixed. - [[TRUNK-4917] - OpenMRS Issues](https://issues.openmrs.org/browse/TRUNK-4917) - [[IDGEN-33] - OpenMRS Issues](https://issues.openmrs.org/browse/IDGEN-33) - Under the epic of [Encounter Diagnosis](https://issues.openmrs.org/browse/TRUNK-5015) \* [[TRUNK-5335] - OpenMRS Issues](https://issues.openmrs.org/browse/TRUNK-5335) \* [[TRUNK-5336] - OpenMRS Issues](https://issues.openmrs.org/browse/TRUNK-5336) \* [[TRUNK-5337] - OpenMRS Issues](https://issues.openmrs.org/browse/TRUNK-5337) \* [[TRUNK-5343] - OpenMRS Issues](https://issues.openmrs.org/browse/TRUNK-5343) \* [[TRUNK-5346] - OpenMRS Issues](https://issues.openmrs.org/browse/TRUNK-5346) \* [[TRUNK-5364] - OpenMRS Issues](https://issues.openmrs.org/browse/TRUNK-5364) \* [[TRUNK-5347] - OpenMRS Issues](https://issues.openmrs.org/browse/TRUNK-5347) \* [[TRUNK-5348] - OpenMRS Issues](https://issues.openmrs.org/browse/TRUNK-5348) \* [[TRUNK-5349] - OpenMRS Issues](https://issues.openmrs.org/browse/TRUNK-5349) \* [[TRUNK-5352] - OpenMRS Issues](https://issues.openmrs.org/browse/TRUNK-5352) \* [[TRUNK-5353] - OpenMRS Issues](https://issues.openmrs.org/browse/TRUNK-5353) \* [[TRUNK-5354] - OpenMRS Issues](https://issues.openmrs.org/browse/TRUNK-5354) **Tickets below still need more work.** > [@OpenMRS Platform 2.2 Ticket Follow up](https://talk.openmrs.org/t/openmrs-platform-2-2-ticket-follow-up/18059/3): > > [[TRUNK-4791] - OpenMRS Issues](https://issues.openmrs.org/browse/TRUNK-4791) (Someone, could be @ssmusoke can help change it to “ready for work”. I lack the privilege.) > > [[TRUNK-5015] - OpenMRS Issues](https://issues.openmrs.org/browse/TRUNK-5015) > > We also have lots of issues under “code review”. Some of them look like they can be closed. I just need the community’s attention here. > > [[TRUNK-5360] - OpenMRS Issues](https://issues.openmrs.org/browse/TRUNK-5360) > > [[TRUNK-5340] - OpenMRS Issues](https://issues.openmrs.org/browse/TRUNK-5340) (Needs to be re-assessed, @wyclif said of moving it to type RESTWS) [[TRUNK-5350] - OpenMRS Issues](https://issues.openmrs.org/browse/TRUNK-5350)[[TRUNK-5341] - OpenMRS Issues](https://issues.openmrs.org/browse/TRUNK-5341)[[PLAT-30] - OpenMRS Issues](https://issues.openmrs.org/browse/PLAT-30) Those defined above are under status “code review”. > [@OpenMRS Platform 2.2 Ticket Follow up](https://talk.openmrs.org/t/openmrs-platform-2-2-ticket-follow-up/18059/2): > > [[TRUNK-5345] - OpenMRS Issues](https://issues.openmrs.org/browse/TRUNK-5345)[[TRUNK-5342] - OpenMRS Issues](https://issues.openmrs.org/browse/TRUNK-5342)[[TRUNK-4755] - OpenMRS Issues](https://issues.openmrs.org/browse/TRUNK-4755)[[IDGEN-42] - OpenMRS Issues](https://issues.openmrs.org/browse/IDGEN-42) > > [[TRUNK-5339] - OpenMRS Issues](https://issues.openmrs.org/browse/TRUNK-5339) Those define above are under status “Ready for work” So I’m not sure whether we gonna bump them out of platform 2.2 batch 😨 cc: @dkayiwa, @darius , @wyclif ---
**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:** [June 4, 2018, 1:51pm UTC](https://talk.openmrs.org/t/platform-2-2-release-is-on-4th-june-2018/16399/4 "2018-06-04T13:51:33Z")
Thanks @samuel34! We _cannot_ do a 2.2 release currently because, unfortunately, the Support for Encounter Diagnosis functionality is only partially complete: > This functionality needs to be completed and tested (included a migration path for current implementations). I haven’t been following this closely, but my sense is there’s a fair amount of work left to be done here. Alternatively, we could see if we could (temporarily) revert the work done on this and do the 2.2 release without any of the Encounter Diagnosis changes, but this may be non-trivial as well. Thanks! Take care, Mark ---
**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:** [June 4, 2018, 1:55pm UTC](https://talk.openmrs.org/t/platform-2-2-release-is-on-4th-june-2018/16399/5 "2018-06-04T13:55:06Z")
Also, it looks like “Support of Provider Roles” has not been implemented (but this isn’t as much of an issue, because it’s not partially complete, so I think we could do a 2.2 release as-is without it). > Take care, Mark ---
**Author:** ![samuel34](https://talk.openmrs.org/user_avatar/talk.openmrs.org/samuel34/32/17813_2.png) [@samuel34](https://talk.openmrs.org/u/samuel34)\ **Post date:** [June 4, 2018, 2:16pm UTC](https://talk.openmrs.org/t/platform-2-2-release-is-on-4th-june-2018/16399/6 "2018-06-04T14:16:33Z")
> [@mogoodrich](#): > > We cannot do a 2.2 release currently because, unfortunately, the Support for Encounter Diagnosis functionality is only partially complete: I agree with you. I think we should look forward to extending the release date of platform 2.2. ---
**Author:** ![irenyak1](https://talk.openmrs.org/user_avatar/talk.openmrs.org/irenyak1/32/6339_2.png) [@irenyak1](https://talk.openmrs.org/u/irenyak1)\ **Post date:** [June 19, 2018, 8:24am UTC](https://talk.openmrs.org/t/platform-2-2-release-is-on-4th-june-2018/16399/7 "2018-06-19T08:24:18Z")
Hello @mogoodrich following the above posts about this [issue](https://issues.openmrs.org/browse/TRUNK-5015) that hadn’t been completed, how far is the work on it now? Could we say we are nearing the release date or we still have to push it a head and for how long? Thanks 😄 ---
**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:** [June 19, 2018, 12:49pm UTC](https://talk.openmrs.org/t/platform-2-2-release-is-on-4th-june-2018/16399/8 "2018-06-19T12:49:50Z")
@irenyak1 I haven’t been working on the Encounter Diagnoses ticket myself but have been tracking the progress since I know it will break implementations if not added with a proper migration strategy. It does look like someone new has picked up the one remaining ticket and @dkayiwa has been guiding them but it looks like they may still be in the beginning stages.