Wiki Spaces

Documentation
Projects
Resources

Get Help from Others

Q&A: Ask OpenMRS »
Discussion: OpenMRS Talk »
Real-Time: IRC Chat

Resources

Skip to end of metadata
Go to start of metadata

The OpenMRS community can only support a limited number of released versions, since supporting a release takes peoples' time and effort (e.g., backporting bug fixes). As a community, we have agreed to do our best to support up to three versions. This means we strive to maintain the current release along with the two prior minor versions.

What does it mean to be End Of Life (EOL)?

Bugs are no longer backported to these versions

The core team will not be backporting and committing patches to that release's folder.

No longer supported by community developers

Bug reports for end of life versions will be answered with 'please upgrade to a supported version and confirm it is still an issue'. We will not be releasing new maintenance point releases in that line.

 

Unsupported Releases

  • No labels

5 Comments

  1. As of February 2015, the current versions of OpenMRS are 2.1, 2.0, and 1.9.  While we will release OpenMRS 2.2 next month, I would propose that we revisit our EOL policy and consider adjusting it for two reasons:

    1. We have switched to scheduled, bi-annual releases since creating the EOL policy, and
       
    2. OpenMRS 2.x has not yet reached feature parity with OpenMRS 1.9.  Hopefully this will change by OpenMRS 2.3 in September 2015.

    At a minimum, I believe we shouldn't start "counting" OpenMRS 2 versions against the EOL policy until OpenMRS 2 has reached feature parity with OpenMRS 1.9.  We shouldn't stop supporting 1.9 until we have at least one very viable upgrade pathway from OpenMRS 1.9 to OpenMRS 2.

    Also, we have not addressed EOL of the OpenMRS Platform, which began it's own journey as of OpenMRS Platform 1.10.  I'm assuming that we will adopt the same EOL policy for the platform – i.e., supporting the last three minor version releases.  A viable alternative would be to support the last three minor versions of the platform that are used in a supported community distribution of OpenMRS.  For example, let's say some day we are supporting these three versions of OpenMRS:

    • OpenMRS 3.9 (using platform 2.4)
    • OpenMRS 4.0 (using platform 2.7)
    • OpenMRS 4.1 (using platform 3.1)

    At that point, are we supporting platform 3.1, 3.0, and 2.9?  Or platform 3.1, 2.7, and 2.4?  I would lean toward the latter.  As a community, we should decide and update this EOL policy accordingly.

    1. My interpretation has been:

      • OpenMRS 2 is a distinct product and should have its own EOL policy. (Current OpenMRS 2.1, no EOL yet since there are only 2 releases so far)
      • OpenMRS Platform (1.2 through 1.11) is a distinct product and should have its own EOL policy. (Current version is Platform 1.11, EOL 1.8 and older)
      1. OpenMRS has gone from 1.0 to 2.1 (so far).  We didn't introduce a separate "platform" until OpenMRS Platform 1.10.                                                                                                                                               / 

        OpenMRS Platform born as of Platform 1.10

        That said, retroactively calling everything we did prior to releasing OpenMRS 2 platform might be an easier story to tell.

        1. "That said, retroactively calling everything we did prior to releasing OpenMRS 2 platform might be an easier story to tell."

          The above is at least what several of us have been attempting to explain. (smile)

          1. The above is at least what several of us have been attempting to explain. (smile)

            Well, why didn't you just say that? (tongue)