On 15 February 2018 at 20:02, Enrico Ferreguti <[email protected]> wrote: > 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. >
I think that wiki page is just being prepared so it's ready for the final release -- in any case API freeze isn't in place until the final release. The thinking here is that it's better to hold off the freeze for as long as possible, as we don't want to be constrained by a frozen API while fixing bugs. Better to hold off the freeze and have plugins not available immediately on release then be stuck with a bug due we can't fix for the next 3-4 years due to frozen API. Thanks for the understanding, Nyall _______________________________________________ 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
