<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">2016-12-06 10:47 GMT+01:00 Paolo Cavallini <span dir="ltr"><<a href="mailto:cavallini@faunalia.it" target="_blank">cavallini@faunalia.it</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">Il 06/12/2016 09:20, Régis Haubourg ha scritto:<br>
<br>
> @Paolo, I think we are not yet in polishing step, some really low level<br>
> things still need to be broken and rebuilt. See<br>
> there: <a href="https://github.com/qgis/qgis3.0_api/issues" rel="noreferrer" target="_blank">https://github.com/qgis/qgis3.<wbr>0_api/issues</a><br>
<br>
</span><span class="">Yeas, as I wrote:<br>
<br>
> Could we set some of the issues [0] as blockers?<br>
<br>
</span>> [0]<a href="https://github.com/qgis/qgis3.0_api/issues" rel="noreferrer" target="_blank">https://github.com/qgis/<wbr>qgis3.0_api/issues</a><br>
<br>
IMHO separating "nice to have" from crucial stuff will help us deciding<br>
where to channel efforts, and when to draw a line.<br><div class="HOEnZb"><div class="h5"><br></div></div></blockquote><div><br></div><div>OK, this is at least one thing I can do with labels during the code sprint :)  </div></div></div></div>