German, I think the best way would be to:
1) File a ticket, targetted at 2.18 and marked as Sever/Regression
2) Make a PR containing an automated testcase showing the problem
3) Add a revert of the offending commit in the PR, showing how
it fixes the testcase.
Do you agree, Victor ?
On Tue, Oct 18, 2016 at 10:24:15AM -0500, Germán Carrillo wrote:
> 2016-10-18 8:42 GMT-05:00 Sandro Santilli <s...@kbt.io>:
> > https://github.com/qgis/qgis/commit/61a10df45283a47782bf49ac62f9c5
> > e5f9b27b21
> Hi All,
> what would be the way to deal with this?
> It's currently preventing me from pushing my final commit to this PR ,
> which I hope can make it into QGIS v.2.18.
>  https://github.com/qgis/QGIS/pull/3591
Qgis-developer mailing list
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer