We are considering increasing the minimum version of OpenMRS that future versions of the reporting module will require. Currently we support all releases starting at OpenMRS 1.6, which has now reached end of life. We would like to consider increasing it to a minimum of OpenMRS 1.7, perhaps higher.
There are a variety of good reasons to increase the minimum version requirement of OpenMRS in future releases of the reporting module - it will allow us to support more recent OpenMRS features like Visits and Program Locations for example. It will also allow us to take advantage of a broader range of technical features, making the module more robust. Finally, it will be a lot easier to support. Ensuring that a module is backwards-compatible across a large number of releases is not an easy task and often requires some real compromises in functionality.
However, moving reporting up to, say, 1.8 or 1.9 as a minimum version for it's primary development line does not mean that we will no longer support the 1.6-compatible module in it's current form, as well as continue to address any critical bug fixes in the 1.6-compatible module with point releases. But this would move it into a "maintenance mode", similar to how the 1.6.x branch of OpenMRS has been maintained but does not have the new features available in 1.9. Does this make sense?