It would be a good thing IMO to report API changes with every build if we can. I asked a question on Stackoverflow.com about how to do this a while ago.
http://stackoverflow.com/questions/6596364/tracking-c-lib-public-api-changes - Nathan On Thu, Dec 8, 2011 at 6:03 PM, Paolo Cavallini <[email protected]>wrote: > Il 07/12/2011 17:22, Marco Hugentobler ha scritto: > > > Finally it happened: > > During recent reorganisation of some print composer classes, I broke the > 1.x API. The > > change won't affect many plugins (maybe mapbook?) and the changes are > straightforward > > (some methods are in QgsComposition instead of QgsComposerView now). > Hi. > I think it would be good, at least when the changes are simple, to keep > plugins > updated, so we can continue testing Master without breaking too many > things. > Is this feasible? > Thanks. > > -- > Paolo Cavallini - Faunalia > www.faunalia.eu > Full contact details at www.faunalia.eu/pc > _______________________________________________ > Qgis-developer mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/qgis-developer >
_______________________________________________ Qgis-developer mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/qgis-developer
