I'm not sure we need to break the project here though right? The xml can stay the same just the API and UI is different.
On Tue, Feb 7, 2017 at 8:01 PM, Paolo Cavallini <[email protected]> wrote: > Il 07/02/2017 10:59, Nyall Dawson ha scritto: > > > Well, ideally not. Currently we only break projects which rely on very > > old features (such as 1.x labeling, conversion from old symbology, > > some composer features from maybe 2.6 or earlier). None of these > > breaks are ever likely to be encountered by users. > > > > But breaking data defined transparency may. > > IMHO the break is not desirable, but acceptable, if the advantage is > more consistency. > I think we can prepare a short Migration guide pointing out all the > points to be taken care of/check/modify for the end user. > Cheers. > -- > Paolo Cavallini - www.faunalia.eu > QGIS & PostGIS courses: http://www.faunalia.eu/training.html > https://www.google.com/trends/explore?date=all&geo=IT&q=qgis,arcgis > _______________________________________________ > Qgis-developer mailing list > [email protected] > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer >
_______________________________________________ Qgis-developer mailing list [email protected] List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
