Hi Enrico, Even if the API is not officialy frozen, you can consider it pretty much stable, and I think it's safe to update your plugin now.
If anything changes from now on, I guess that we could ask to send a mail on this list with [API BREAK] subject, but it's very likely to happen. http://python.qgis.org/api/ is not up to date (misses the QgsMessageBar.MessageLevel move to Qgis.MEssageLevel) but will be updated in the next 48 hours. It is 3 weeks old and apart from MessageLevel, I don't think there was big changes to the API for plugins authors. Best wishes, Denis Le jeu. 15 févr. 2018 à 05:02, Enrico Ferreguti <[email protected]> a écrit : > Hi all, In github wiki I read that: " QGIS 3 has entered feature freeze. > It's, therefore, time to port your plugin. But be aware that the *API is > not freezed yet*. " > > Me and many other plugin developers are partecipating to QGIS3 migration > effort. > I'm handling issues notifications related to API break, ( > https://github.com/enricofer/go2streetview/issues/35, > https://github.com/enricofer/go2mapillary/issues/9) and I would know when > API will be stable? Should we expect breaks till the final release? > > I understand that core devs are working hard to make next release more > stable, I would only know how to schedule my time contribution. > > Many Thanks. > Enrico Ferreguti > _______________________________________________ > 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
