Adopting Semantic Versioning for OCL for OpenMRS

Tags: #<Tag:0x00007fcebc530330>

Currently the versioning scheme that we’re using for OCL for OpenMRS is… a little inconsistent across environments. In Jira we have the following releases:

  • 1.0.1: MVP
  • OCLOMRS v2
  • OCLOMRS v1
  • 1.1.0: MVP+
  • 1.0.0: MVP

I’d like to try to standardise this on SemVer, which we use for OpenMRS and it’s modules and detach this from expectations about the product completion (i.e., it’s MVP status). Currently, I’ve been using something similar to this scheme for versioning released builds, so the current version in all systems in OCLOMRS-v1.0.4 (because I ended up tagging a few minor tweaks before everything got working).

I would suggest that the “next version” of OCL for OpenMRS, which includes the ability to sort answers and filter retired concepts (and is likely to include more before we release it) be tagged as 1.1.0 (new functionality, no breaking changes).

Thoughts? Comments?

@hadijah315 @grace @michaelbontyes @suruchi

1 Like

We should definitely go for standardise. Thanks for SemVer, Ian.