Hi Nathan, If we can add a warning batch that points to possible problems... What more can we want? Nice idea!
Does it do the checks on plain source code or does it need some runtime information (so that e.g. only plugins with test suite can be checked and only the parts covered by tests are checked)? Cheers, Matthias On 08/03/2015 08:54 AM, Nathan Woodrow wrote: > Hey Paolo, > > 100% that is what made me think of this when talking to the Python > devs. We should do as much as we can to help people get from A to B > without feeling lost. Doing this in practice is a lot harder but I > think we can lean on tools made by others to help us here. > > Regards, > > On Mon, Aug 3, 2015 at 4:52 PM, Paolo Cavallini <cavall...@faunalia.it > <mailto:cavall...@faunalia.it>> wrote: > > Il 02/08/2015 14:01, Nathan Woodrow ha scritto: > > > Thoughts? > > Very good idea, thanks Nathan. Please consider that many, if not most, > of our plugin devs are relatively new devs, so any way of > smoothing out > their path will be welcomed and important for an effective > transition. I > would suggest adding to the warning you mention also a link to a > detailed howto. > All the best. > > -- > Paolo Cavallini - www.faunalia.eu <http://www.faunalia.eu> > QGIS & PostGIS courses: http://www.faunalia.eu/training.html > _______________________________________________ > Qgis-developer mailing list > Qgis-developer@lists.osgeo.org <mailto:Qgis-developer@lists.osgeo.org> > http://lists.osgeo.org/mailman/listinfo/qgis-developer > > > > > _______________________________________________ > Qgis-developer mailing list > Qgis-developer@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/qgis-developer
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
