Could this be regarded as a bug in the plugin manager? In that case it should be OK to fix it in a point release.
Håvard On 11.03.2019 14:31, Borys Jurgiel wrote:
The reason the plugin manager sends just "?qgis=3.4" was because the point releases ("micro" versions) are expected to only provide bugfixes and not new features. After some thinking, I guess this approach is wrong and a bug is also a reason to prevent the plugin from installing. It's easy to change it in master, I'm not sure if it we should do it in a point release of the LTR... Another place to change would be the repository, as it also cuts off the point release part. For example, the OpenLayers Plugin has minimumQgisVersion=3.0.1 and is visible here: http://plugins.qgis.org/plugins/plugins.xml?qgis=3.1 but not here: http://plugins.qgis.org/plugins/plugins.xml?qgis=3.0.2 Regards, Borys Dnia poniedziałek, 11 marca 2019 13:02:19 CET Havard Tveite pisze:I just experienced a problem with a plugin. The plugin uses the optional "is_child_algorithm" parameter of the processing.run function. That parameter was introduced in 3.4.5 (LTR). I therefore set "qgisMinimumVersion=3.4.5" in the plugin's metadata.txt. It turned out that this caused the plugin not to be available for the current LTR, probably because "Parameters" is set to "?qgis=3.4" in the Plugin manager in 3.4.5. Changing to "qgisMinimumVersion=3.4", makes the plugin show in the plugin manager, but that also makes it available in 3.4.4 and earlier 3.4 versions (where it will fail with an unexpected keyword argument for processing.run...). Could "micro" version be included in the Plugin manager "Parameters", or is this something that will have to be handled in the plugin code? Håvard
_______________________________________________ QGIS-Developer mailing list [email protected] List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
