[Qgis-developer] OpenLayers plugin release and Python API

[Pirmin Kalberer]

Hi Nathan,

Am Mittwoch, 23. Januar 2013, 16.09:43 schrieb Nathan Woodrow:
> 
> We are preparing for 2.0 so the plan has always been to break API and
> remove old unused methods.
> 
> The select API will break again soon once Martin merges his new vector
> API.

If it's the plan to break plugins then I wait with the next update until 2.0 
is released.
Other OSS projects I'm working with care more for their users. They release a 
new API with a major version and deprecate the old one. The deprecated API 
remains available for at least one release. I'm fine with removing old 
labelling, etc., but not with breaking the plugin API from 1.8 to 2.0 without 
proper deprecation.

Pirmin

> 
> - Nathan
> From: Pirmin Kalberer
> Sent: 24/01/2013 9:58 AM
> To: qgis-dev
> Subject: [Qgis-developer] OpenLayers plugin release and Python API
> breaks
> Hi all,
> 
> I found the time for an OpenLayers plugin release with merged pull requests
> for Stamen map support and fixes for Python API breaks in master branch (See
> https://twitter.com/PirminKalberer/status/294226472707715072 for credits).
> The second point was quite annoying for many users and myself. It is a
> really bad practice to break the API without deprecation messages when
> calling these methods. There should be enough time (at least one minor
> version) for developers for updating their plugins. In this case it would
> have been easy to keep the old API and add a deprecation message similar to
> http://code.activestate.com/recipes/391367-deprecated/
> 
> Regards
> Pirmin
-- 
Pirmin Kalberer
Sourcepole  -  Linux & Open Source Solutions
http://www.sourcepole.com