If you are looking for downloadable builds of OpenMRS, see download.openmrs.org.
A running OpenMRS application displays its version in the bottom footer. A small red "i" will appear next to an expected database version that is different that what the current code is thinking it is working against. If this is the case, the file labeled openmrs-X.Y-to-latest-mysqldiff.sql should be run ("source"ed) on the current database.
The format for OpenMRS versions:
How/when to Choose a Version Number
We follow OpenMRS follows the Apache Versioning conventions Semantic Versioning conventions for the platform, reference application, and community supported modules. We encourage everyone to adopt this versioning approach for their code.
The major version number is changed when there are large incompatible changes – e.g., methods are being removed from the API. These should be rare.
The minor version should change when new features are added or the changes being made will make the prior version incompatible with the new changes. Minor versions should be backwards compatible with older minor versions, but may not be future compatible. For example, if a module requires OpenMRS 1.4, then it should still work with 1.5, but may not work with 1.3.
Sometimes Also referred to as "Patch." Maintenance releases represent bug fixes (maintenance) and should be both forward and backward compatible. For example, if your code works with 1.5.2, it should work with 1.5.1 and 1.5.7.