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.