<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html lang="en">
<head><meta http-equiv="Content-Type" content="text/html;">
<title>Scalix message content</title>
<style type="text/css">
<!--
.Normal { text-align: left; text-indent:0pt; margin-top:0pt; margin-bottom:0pt; font-family: Arial; font-size: 12pt; }
.Default_Paragraph_Font {font-family: Arial; color: Black; background-color: white ; font-size: 12pt; font-weight: normal; font-style: normal; font-variant: normal; vertical-align: normal; text-decoration: none;}
div.ltTOCtitle { font-family: Verdana; font-size: 8pt; font-weight: bold; text-align: center;}
div.ltTOCl1 { font-family: Verdana; font-size: 8pt; font-weight: bold; margin-left:32pt; text-indent:-32pt;}
div.ltTOCl2 { font-family: Verdana; font-size: 8pt; font-weight: bold; margin-left:40pt; text-indent:-32pt;}
div.ltTOCl3 { font-family: Verdana; font-size: 8pt; font-weight: bold; margin-left:48pt; text-indent:-32pt;}
div.ltTOCl4 { font-family: Verdana; font-size: 8pt; font-weight: bold; margin-left:56pt; text-indent:-32pt;}
div.ltTOCl5 { font-family: Verdana; font-size: 8pt; font-weight: bold; margin-left:64pt; text-indent:-32pt;}
div.ltTOCl6 { font-family: Verdana; font-size: 8pt; font-weight: bold; margin-left:72pt; text-indent:-32pt;}
-->
</style>
</head>
<body>
<div class="Normal"><span style='font-size: 10pt; '>At the moment I'm a little
bit frightened about the release plans and the backward compatibility of PyQgis.
</span></div>
<br>
<div class="Normal"><span style='font-size: 10pt; '>We are starting to develop
special Plugin applications for business processes in our government now. In
former times they were solved by ArcView3 plugins. Thus for us it is an
absolutely must to have long term stability of the PyQgis API. It would be a
worst case scenario to have to redesign our plugins and applications due to
changes of the PyQgis API every release. Please be aware of this
fact.</span></div>
<br>
<div class="Normal"><span style='font-size: 10pt; '>Regards</span><br><span style='font-size: 10pt; '>Horst</span></div>
<br>
<div class="Normal"><span style='font-size: 10pt; '>------------------------------------------------</span></div>
<br>
<div class="Normal"><span style='font-size: 10pt; '>Dr. Horst
Düster</span><br><span style='font-size: 10pt; '>GIS-Koordinator, Stv.
Amtschef</span></div>
<br>
<div class="Normal"><span style='font-size: 10pt; '>Kanton
Solothurn</span><br><span style='font-size: 10pt; '>Bau- und
Justizdepartement</span><br><span style='font-size: 10pt; '>Amt für
Geoinformation</span><br><span style='font-size: 10pt; '>SO!GIS
Koordination</span><br><span style='font-size: 10pt; '>Rötistrasse
4</span><br><span style='font-size: 10pt; '>CH-4501 Solothurn</span></div>
<br>
<div class="Normal"><span style='font-size: 10pt; '>Telefon ++41(0)32 627 25
32</span><br><span style='font-size: 10pt; '>Telefax ++41(0)32 627 22
14</span></div>
<br>
<div class="Normal"><span style='font-size: 10pt; '>mailto:horst.duester@bd.so.ch</span><br><span style='font-size: 10pt; '>http://www.agi.so.ch</span></div>
<br>
<div class="Normal"><span style='font-size: 10pt; '>-----Ursprüngliche
Nachricht-----</span><br><span style='font-size: 10pt; '>Von: Martin Dobias
[mailto:wonder.sk@gmail.com]</span><br><span style='font-size: 10pt; '>Gesendet
am: Dienstag, 3. Juni 2008 19:15</span><br><span style='font-size: 10pt; '>An:
Tim Sutton</span><br><span style='font-size: 10pt; '>Cc:
qgis-developer@lists.osgeo.org</span><br><span style='font-size: 10pt; '>Betreff:
Re: [Qgis-developer] Release plans for QGIS 0.11.0 and on
to</span><br><span style='font-size: 10pt; '>1.0</span></div>
<br>
<div class="Normal"><span style='font-size: 10pt; '>On Mon, Jun 2, 2008 at 3:51
PM, Tim Sutton <tim@linfiniti.com>
wrote:</span><br><span style='font-size: 10pt; '>> My idea was along these
lines:</span><br><span style='font-size: 10pt; '>></span><br><span style='font-size: 10pt; '>>
- on 1.0 release branch and maintain that as 1.x stable branch
with</span><br><span style='font-size: 10pt; '>> branches for releases coming
off that</span><br><span style='font-size: 10pt; '>> - continue work in
trunk to become the eventual
2.0</span><br><span style='font-size: 10pt; '>></span><br><span style='font-size: 10pt; '>>
If fixes are made to 1.x branch which can be ported to 2.0 branch
(or</span><br><span style='font-size: 10pt; '>> vica verca) aply them
manually, but I think we should proceed with
2.0</span><br><span style='font-size: 10pt; '>> work with no concern for the
most part of maintaining API</span><br><span style='font-size: 10pt; '>>
compatibility. It would be good to change the plugin API as little
as</span><br><span style='font-size: 10pt; '>> possible but even that should
not be an overwhelming constraint.</span></div>
<br>
<div class="Normal"><span style='font-size: 10pt; '>This plan sounds good to
me!</span></div>
<br>
<div class="Normal"><span style='font-size: 10pt; '>Just one note: plugin API in
QGIS consists or core and gui libs
API,</span><br><span style='font-size: 10pt; '>QgisInterface instance and
QgisPlugin interface which is subclassed
by</span><br><span style='font-size: 10pt; '>plugins. So it's hard to speak
about not breaking plugin API if we
do</span><br><span style='font-size: 10pt; '>refactoring in QGIS
libs...</span></div>
<br>
<div class="Normal"><span style='font-size: 10pt; '>Martin</span><br><span style='font-size: 10pt; '>_______________________________________________</span><br><span style='font-size: 10pt; '>Qgis-developer
mailing
list</span><br><span style='font-size: 10pt; '>Qgis-developer@lists.osgeo.org</span><br><span style='font-size: 10pt; '>http://lists.osgeo.org/mailman/listinfo/qgis-developer</span></div>
</body>
</html>