Il 10/09/2015 10:44, Blumentrath, Stefan ha scritto: > Recently, I updated the GarminCustomMap plugin which I developed a few > years ago, because users reported that it crashes QGIS. > > > > Unfortunately, the bug reports (the plugin uses the QGIS bug tracker > system and repository) never were forwarded to me, so I noticed them > only with a significant delay… > > So I was wondering if it is preferred that plugin authors use their own > versioning and bug tracking solution (github in my case)?
IMHO using only GitHub is the simplest option, and it works well enough. Of course, I do not like it being proprietary software, but since QGIS code is already there, I think we can't complain. > Furthermore, the plugin worked nicely with QGIS 2.0 to 2.4. While > problems were reported for 2.6 and later. I did not change the > plugin-code in that period, so issues must have been introduced by > external changes (likely in GDAL/OGR and their windows packages). I see > that it is impossible to prevent such issues, as plugins are by nature > not core. But how should plugin authors deal with that? Simply send bug > reports back to QGIS (in my case it came from there…)? Yes, I think that's the correct approach. Thanks for the report. -- Paolo Cavallini - www.faunalia.eu QGIS & PostGIS courses: http://www.faunalia.eu/training.html _______________________________________________ Qgis-developer mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/qgis-developer
