Backend Contributions to EMR releases: Why and How

Community
, ,
1

Over the last few days a few folks have reminded me that backend or api-level contributions weren’t getting explicit credit in our release notes.

Thanks to guidance from the Platform Team today, I reviewed our 3.4 Release contributions in more detail and found the various backend OMODs that needed to be counted. In total this increased our total “PRs Contributed” metric from 185 PRs to 226! And also helped us catch quite a bit of org-level and individual-level contributions that deserve explicit recognition.

Recognition is now up-to-date in the draft EMR version 3.4 Release notes here: https://openmrs.atlassian.net/wiki/x/AQDuFg

Video Explainer on Why this mattered:

And now the harder part: Explaining exactly how we find and count these contributions. Basically:

  1. Compare the Release Diffs here to see which backend artifacts/omods have had a version change in the release: Comparing 3.3.1...3.4.0-rc.2 · openmrs/openmrs-distro-referenceapplication · GitHub
  2. Generate release notes for each new version of an OMOD/backend component, e.g. Release 2.7.4 (Compared to 2.7.2; Example of Auto-Generated Notes) · openmrs/openmrs-core · GitHub (in this example, since the last 3.3 EMR release used Core 2.7.2, I specifically generated these release notes to compare with the version used in 3.4 EMR, which is Core 2.7.4, to make sure we don’t miss any contributions).
  3. Copy-paste the contributions for each OMOD into the Chart-generating spreadsheet, here: Release Org Contributions to PRs - Google Sheets

Explainer video:

FYI for @beryl @wodpachua @suubi7 @mseaton @dkayiwa

8 Likes
2

That’s fantastic news!

Thanks @grace the contributions to, backend and API-level are often forgotten. It’s truly vital to acknowledge all the hard work that goes into every aspect of OpenMRS, and this significant increase from 185 to 226 PRs really highlights how much was being missed.

6 Likes