Supported versions: too opaque

[Huite]

The installation guide (https://deltares.github.io/iMOD-Documentation/viewer_install.html) mentions:

You can download the standalone QGIS setup on the QGIS website We recommend downloading a QGIS version > 3.18 here

There are at least two problems with this:

• It tells you a version that is NOT supported (3.18). I think it's more common/easier-to-parse to say which version IS supported (>=3.20). Currently, you read 3.18, and then have to decide it's not the one you want.
• 3.18 is not necessarily clear either: is the entirety of 3.18 not allowed, or does it implicitly stand for 3.18.0? And would 3.18.2 maybe be supported?

Secondly, we should make a plan for whether we'll stick to the latest changes or not. If we do stick to latest changes, we need to assign versions carefully to the plugin. My personal preference is to stick to LTR if possible. But this is something we might be able to test: if new versions of QGIS do not constantly break the plugin, we could stick to latest changes.

On the upside, I think the notice has been removed that the Mesh stuff may be changed without notice? https://qgis.org/pyqgis/master/core/QgsMeshDataset.html

Second, we need a careful changelog detailing which changes in QGIS necessitate changes in the plugin.

[JoerivanEngelen]

FYI: The warning about API changes for meshes is still present on some pages, e.g.: https://qgis.org/pyqgis/master/core/QgsMeshLayer.html So I'm not sure...

[JoerivanEngelen]

I've done done to clear things up:

• I've updated the recommended version in the iMOD-Documentation to >= 3.28
• The Minimum version in the qgis plugin database is set to 3.28

The increase to 3.28 was necessary because we added the IDF widget, which apparently used functionality in the API not present in 3.18. So far, after a 1.5 years, experience is that the the API has been quite stable. A changelog is included in the metadata.txt, where we could add changes made because of changes in QGIS.

Right now, we're running some tests on QGIS 3.30. We could make this the latest version to quickly see if API changes break anything. For this to work better, the test bench needs to be expanded though.

Closing this as it seems less relevant given the stability of the QGIS API the last years. We can re-open this if the situation worsens.