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.<div><br></div><div><a href="http://stackoverflow.com/questions/6596364/tracking-c-lib-public-api-changes">http://stackoverflow.com/questions/6596364/tracking-c-lib-public-api-changes</a><br>
<br>- Nathan<br><br><div class="gmail_quote">On Thu, Dec 8, 2011 at 6:03 PM, Paolo Cavallini <span dir="ltr"><<a href="mailto:cavallini@faunalia.it">cavallini@faunalia.it</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Il 07/12/2011 17:22, Marco Hugentobler ha scritto:<br>
<div class="im"><br>
> Finally it happened:<br>
> During recent reorganisation of some print composer classes, I broke the 1.x API. The<br>
> change won't affect many plugins (maybe mapbook?) and the changes are straightforward<br>
> (some methods are in QgsComposition instead of QgsComposerView now).<br>
</div>Hi.<br>
I think it would be good, at least when the changes are simple, to keep plugins<br>
updated, so we can continue testing Master without breaking too many things.<br>
Is this feasible?<br>
Thanks.<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Paolo Cavallini - Faunalia<br>
<a href="http://www.faunalia.eu" target="_blank">www.faunalia.eu</a><br>
Full contact details at <a href="http://www.faunalia.eu/pc" target="_blank">www.faunalia.eu/pc</a><br>
</font></span><div class="HOEnZb"><div class="h5">_______________________________________________<br>
Qgis-developer mailing list<br>
<a href="mailto:Qgis-developer@lists.osgeo.org">Qgis-developer@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
</div></div></blockquote></div><br></div>