Reference Application 2.11.0 Release Management + Planning

Release Date (November 2020)

Release Manager: @Sharif Magembe

Release Manager Mentor: @Moses Mutesasira

Release Manager Co-Mentor: @tendo kiiza Martyn

Team Members

        -    @Daniel Kayiwa

        - @Grace Potma

       - @Herbert Yiga

       -    @Juliet Wamalwa

       - @Reagan patrick Makoba

 

       

Release TimeLine

Status

Activity

Resources Needed

Duration(once a year)

Completion

 Date

Comments

Status

Activity

Resources Needed

Duration(once a year)

Completion

 Date

Comments

completed

Agreeing  the vision and  the strategic  goal of RoadMap   Activities

Community

Core apps Lead

Once a year

 

Still in process of collaborating with team leads/squads .

completed

Call out on all OMRS Communication channels announcing the commencement of the RoadMap planning Process

TPM

@Grace Potma

@Jennifer Antilla

 

1 week

August 23

 

completed

Identification of volunteer team members for core activities of the group, such as release management, BA, QA , testing

 

TPM Community

Implementers

Individual contributors

Continuous

September 27th 2020 

 

completed

Receive new feature requests from community

Prioritization and Validation of feature requests

Confirmation of feature owners and resourcing to develop feature (or go it alone)

TPM Community

Implementers

Individual contributors

GSOC??

continuous

(2-4 weeks window)

August 30 

2020

 

completed

Commencement of Release Process

Release Manager,  Community Dev's

8-15 Weeks

August 2020

 

completed

Quality Assurance & Testing

QA ,  Community, Community Dev's

4-6 weeks

 

 

completed

Application pushed for community alpha release (or criteria that meets an alpha release)

Release Manager, Community Dev's

4-6 weeks

 

 

 

completed

Beta Release

Release Manager, Community

4-6 weeks

 

 

 

completed

Completion of Release Process & Application Launch

Release Manager

4 weeks

 

 

 

RoadMap Features 

RoadMap   RoadMap planning

Ongoing talk Post for Including SPA module And Here

Objective Lead TBD Objective CO-Lead  @Burke Mamlin

Feature 

Description

Status

Point of  Contact

Comments

Feature 

Description

Status

Point of  Contact

Comments

Removed openmrs-module-spa in  ref-app 2.11.0

in preparation of MICROFRONTENDS

openmrs-spa module

Checkout on Talk for more discussions  https://talk.openmrs.org/t/include-spa-module-in-refapp-2-11/29678/9

And  https://talk.openmrs.org/t/removing-single-page-application-spa-in-ref-app-2-11-0/30315

 

 

completed

see completed tickets

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

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

 

@Burke Mamlin

@Daniel Kayiwa

@Brandon Istenes

Individual contributors

Implementers

We are still in the discussion on talk https://talk.openmrs.org/t/include-spa-module-in-refapp-2-11/29678/9

This is going to leverage the functionality for spa in relation to micro front end process. 

 See the module repository  https://github.com/openmrs/openmrs-module-spa

 

Bug fixes and modifications

We have a number of  Tickets that include bug fixes and feature enhancements in the Reference Application: 

type key summary assignee reporter priority status resolution created updated due

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Check github_changelog_generator to catch work that was done but not ticketed in Jira

 completed

See tickets Fixed

type key summary assignee reporter priority status resolution created updated due

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Community members

Implementers ,devs

Community members called upon to work on these tickets

 

 

 

 

Improve Reference Application Performance

We need to optimize the performance of The reference Application by Revising the Current List of modules and removing some modules whose current usage is low

completed

A number of modules were updated like FHIR  module were updated to fhir2 module as per Reference Application 2.11.0 Release Issue Tracking

And here https://github.com/openmrs/openmrs-distro-referenceapplication/blob/master/pom.xml#L71

We also didnot bundle spa module as per https://talk.openmrs.org/t/removing-single-page-application-spa-in-ref-app-2-11-0/30315

 

@Grace Potma

@Daniel Kayiwa

  1. Update Reference Metadada Packages

2. Removing Covid-19 Concepts For Reference Application 2.11

 

This should be maintained with the newly created metadata packages

There were some changes that were made about covid-19 concepts and we decided to remove them from current refApp 2.11 release according to this talk thread

.https://talk.openmrs.org/t/an-overview-of-the-forthcoming-next-release-for-ref-app-2-11-0/29618/127

We therefore decided to package them in a separate module covid-19 module with this Pull Request such that any implementor can leverage them after uploading covid19 module into an instance

 

   completed

https://github.com/openmrs/openmrs-module-referencemetadata/pull/54

https://github.com/openmrs/openmrs-module-referencemetadata/pull/57

IN PROGRESS

And https://github.com/openmrs/openmrs-module-covid19/pull/1

 

@Sharif Magembe

@Sharif Magembe

 

PROJECT UPDATES

GitHub Link : 

 

 

  • ...

Canvassing for New Ideas & Features

  • Several sources are considered in determining which features get added to OpenMRS, including:

    • OpenMRS implementation site needs

    • OpenMRS priorities

    • Features requests within the issue tracker

    • Needs of ongoing projects(including spa module)

    • Module authors(module maintainers)

    • Needs of ongoing grant-funded projects

    • Implementers' Showcase (Previously called "Scrum of Scrums") every 3 months

    • Discussions from Design Forum

     

  • Other channels:

    • Review of current functionality of current ref and platform apps to identify features that could be improved.

    • Continuous review of competitor applications both open and proprietary systems

    • Feedback from monthly Squad Showcase

Â