Is there a way for tech partners, which are developing their own connectors, to check which minimum DataMiner version is required for a new connector?
Or would it always be the DataMiner version the developer was testing against? As the connector is usually developed on the latest feature release, it would be interesting to check if the connector also runs on older DataMiner versions.
There is no straightforward check to know the absolute minimum supported DataMiner version of a connector. Typically a developer will initially develop against the minimum supported version of DataMiner to support as many users as possible (10.0 at this moment, 10.1 from next month onwards) and indicates this as the minimum required version. Unless it's absolutely crucial to use a new software feature, then the minimum required version will be increased.
In DIS the DataMiner DEV pack of that minimum required version should be used.
When running the DIS validator, it will show when QAction will not be able to compile e.g. because of a method that does not exist yet in that version. The DIS validator will also show if XML tags or options are being used that are also not supported yet.
Do note that the DIS validator will not cover all cases. E.g., it does not know since when really old XML options got introduced, but for the current supported DataMiner versions this should be checkable by the validator. It's also not because a QAction compiles, that it will work correct. E.g. a NotifyProtocol could be accepting an extra item in an object array that is being passed since a certain DataMiner version, so these are things that could slip through the validator checks.