Reference Application 2.6 Release Issue Tracking

Owned by raff
Last updated: May 02, 2017 by Darius Jazayeri
3 min read

Reference Application 2.x releases are different than OpenMRS platform releases (like 1.11.0). Platform releases usually consist of alpha, beta releases and have Sprints to complete tickets in a short span of time. Reference Application 2.x is a collection of modules and hence its release consists of releasing all the modules planned to be included in the 2.x release and testing if all of them function collectively.

In the case of 2.6, the release is planned for the end of April 2017. Though the testing might not be as extensive as a Platform release, a user acceptance testing is necessary. All the modules that are planned to be released in 2.6 need to be in a release ready state and we need your collective collaboration on making this happen.

UAT until 2017/05/03 2 p.m. UTC at http://uat-refapp.openmrs.org/

Release date: 2017/05/04 2 p.m. UTC

Included Modules

Parent tracking issue for these items: 

Module Name

Version    

Point(s) of Contact

JIRA Issue

Maven?

Modulus?

Version/Notes/Description

Module Name

Version    

Point(s) of Contact

JIRA Issue

Maven?

Modulus?

Version/Notes/Description

addresshierarchy

2.10.0

Mark Goodrich

 

Yes

Yes

2.10. has been released (it wasn't included in RA 2.5, should it be added to RA 2.6?)

providermanagement

 

2.5.1

2.6.0

@Mark Goodrich

 

Yes

Yes

2.6.0 has been released

calculation

 

1.2

@Darius Jazayeri
@Mike Seaton

 

Yes

Yes

No changes, use already released 1.2

serialization.xstream

0.2.12

@Mike Seaton

 

Yes

Yes

No changes, use already released 0.2.12

reportingrest

1.8.0

@Mike Seaton@Darius Jazayeri

 

Yes

Yes

1.8.0 has been released

atlas

2.2

@Alexis Duque
@Burke Mamlin
@Darius Jazayeri

 

 

 

No changes, use already released 2.2

appframework

2.10.0

@Darius Jazayeri

 

 

 

Use already released 2.10.0

htmlwidgets

1.9.0

@Mike Seaton@Daniel Kayiwa

 

Yes

No (please upload)

Use released 1.9.0

reporting

1.12.0

@Mike Seaton

 

Yes

 

Already released

metadatasharing

1.2.2

@raff

 

Yes

Yes

Use existing 1.2.2

metadatamapping

1.3.2

@raff

 

Yes

Yes

Use released 1.3.2

htmlformentryui

1.6.2

@Mark Goodrich
@Darius Jazayeri

 

Yes

Yes

Use existing 1.6.2 release

namephonetics

1.6.0

@Mike Seaton

 

 

 

Use existing 1.5 release

idgen

4.4.1

@Mike Seaton
@Daniel Kayiwa 

 

Yes

No (please upload)

Use new 4.4.1 release

dataexchange

1.3.2

@raff

 

Yes

Yes

Use existing 1.3.2 release

metadatadeploy

1.8.1

@Mark Goodrich
@Darius Jazayeri

 

Yes

Yes

Use existing 1.8.1 release

htmlformentry

3.3.2

@Mark Goodrich
@Darius Jazayeri

 

Yes

Yes

Use existing 3.3.2 release

formentryapp

1.4.1

@Darius Jazayeri
@raff
@Cintia Del Rio

 

Yes

No

Use new 1.4.1 release

uiframework

3.10.1

3.11.0

@Darius Jazayeri
@raff

 

Yes

Yes

Use new 3.11.0 release

uilibrary

2.0.4

@Darius Jazayeri
@Rowan Seymour

 

Yes

Yes

No changes, use old 2.0.4 release.

appui

1.8.0

@Mark Goodrich
@Darius Jazayeri

 

Yes

Yes

Use new 1.8.0 release

coreapps

1.12.1

@Cosmin Ioan
@Mark Goodrich
@Darius Jazayeri 

 

 

 

Error rendering macro 'jira' : Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Release 1.12.1 (I'll do it, @raff)

emrapi

1.21.0

@raff
@Mark Goodrich
@Darius Jazayeri

 

Yes

Yes

I just released 1.22.0, so use this instead of 1.21.0. -Darius

 

1.22.0 was causing server startup failure at

https://travis-ci.org/openmrs/openmrs-distro-referenceapplication/jobs/226407253,

reverted to use 1.21.0 -Rafal

uicommons

2.3.0

@Darius Jazayeri

 

 

 

Use newly released 2.3.0

webservices.rest

2.19.0

@Daniel Kayiwa
@raff

 

Yes

Yes

Use newly released 2.19.0

event

2.5

@Daniel Kayiwa
@raff

 

Yes

 

Use existing 2.5 release

allergyui

1.7.0

@Daniel Kayiwa
@Wyclif Luyima

 

 

 

Use new 1.7.0 release

registrationcore

1.7.1

@David DeSimone
@Darius Jazayeri
@raff

 

Yes

 

Error rendering macro 'jira' : Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Use new 1.7.1 release

registrationapp

1.8.0

@David DeSimone
@Darius Jazayeri
@Cosmin Ioan
@Mark Goodrich

 

Yes

Yes

Use new 1.8.0 release

referenceapplication

2.6

@Wyclif Luyima
@Darius Jazayeri

 

 

 

Release 2.6.0 (I'll do it, @raff)

referencedemodata

1.4.3

@Darius Jazayeri
@raff

 

Yes

 

Use existing 1.4.3

referencemetadata

2.6.0

@Daniel Kayiwa
@Darius Jazayeri

 

Yes

 

Use new 2.6.0 release

chartsearch

2.0

@Kaweesi Joseph
@Daniel Kayiwa

 

Yes

Yes

Use existing 2.0.

appointmentscheduling

1.8.0

@Mark Goodrich

 

Yes

Yes

Use new 1.8.0 release

appointmentschedulingui

1.6.0

@Mark Goodrich

 

Yes

Yes

Use new 1.6.0 release

legacyui

1.3.0

@Daniel Kayiwa

 

 

 

Use new 1.3.0 release

reportingcompatibility

2.0.2

@Daniel Kayiwa

 

 

 

Use existing 2.0.2 unless Daniel release 2.0.3 by tomorrow

open web apps

1.7.0

@Saptarshi Purkayastha

@raff

@Daniel Kayiwa

 

Yes

 

Use new 1.7.0 release

adminui

1.2.2

@Daniel Kayiwa

 

 

 

Use new 1.2.2 release

FHIR

1.7.0

@Suranga Kasthurirathne

 

Yes

No (maintainers please upload)

Use new 1.7.0 release

reportingui

1.3.0

@Mike Seaton

 

Yes

 

Use new 1.3.0 release (newly added)

Additional Release Items

Parent tracking issue for these items: 

Item Name

Point(s) of Contact

JIRA Issue

Notes/Description

Item Name

Point(s) of Contact

JIRA Issue

Notes/Description

Include latest CIEL concept dictionary

 

 

 

Deploy Reference Application 2.6 to UAT

 

 

 

Reference Application 2.6 UAT

 

 

 

Release of Reference Application 2.6

 

 

 

Sample

Module Name

Point(s) of Contact

JIRA Issue

Status

Nexus?

Modulus?

Released Version/Notes/Description

Module Name

Point(s) of Contact

JIRA Issue

Status

Nexus?

Modulus?

Released Version/Notes/Description