|
On 23/10/2012 09:28, Sandro Santilli
wrote:
On Mon, Oct 22, 2012 at 09:35:05PM +0200, Werner Macho wrote:Hi!Short answer from me +1 and go ahead .. As I remember we all knew that on the way to 2.0 there will be some API Changes - but as long as it improves QGIS at a Project I see no Problem for it .. The only thing you are worrying about are the Plugins .. but hey - there is still 1.8 ..Assuming it's going to be maintained... As I'm not a developer, I can only gently mention my wishes: Back when the 1.7.x version was the "stable" a lot of good effort was put into implementing bug fixes, eventually leading to an excellent 1.7.4. I hope now, with 2.0 bringing these API changes and breaking plugins etc, that a 1.8.x stable will be maintained "for the duration" until the new version settles, and plugin developers can catchup. Thanks, Micha And once all those changes settled in (upcoming) 2.0 - from my point of view it would be time for a new release .. Probably we should introduce a max.Version to plugins too? ;)I think all changes should be made backward compatible unless the development cost in doing so is higher than the development cost of upgrading all plugins. --strk; _______________________________________________ Qgis-developer mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/qgis-developer This mail was received via Mail-SeCure System. -- Micha Silver 052-3665918 |
_______________________________________________ Qgis-developer mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/qgis-developer
