Re: [Qgis-developer] QGIS 2.0 and beyond
Giovanni could you do a triage of the blocker issue queue - it seems like some could be removed (e.g. http://hub.qgis.org/issues/7619 could be closed?). I checked the queue and cleaned it as much as possible. There is a small list of tickets that probably can be closed(*), but the other 71 are pretty much confirmed (almost all regressions). There is a bit of everything, big issues with edit tools, wfs client, ftools (many with memory leaks), printing, etc. (*) http://hub.qgis.org/issues/6383 http://hub.qgis.org/issues/6978 http://hub.qgis.org/issues/7458 http://hub.qgis.org/issues/7940 http://hub.qgis.org/issues/7668 ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] QGIS 2.0 and beyond
Hi Thanks very much Giovanni. We are holding a PSC meeting tomorrow to plan the release strategy and your revisions will come in handy for that. Regards Tim On Sun, Jun 2, 2013 at 11:30 AM, Giovanni Manghi giovanni.man...@faunalia.pt wrote: Giovanni could you do a triage of the blocker issue queue - it seems like some could be removed (e.g. http://hub.qgis.org/issues/7619 could be closed?). I checked the queue and cleaned it as much as possible. There is a small list of tickets that probably can be closed(*), but the other 71 are pretty much confirmed (almost all regressions). There is a bit of everything, big issues with edit tools, wfs client, ftools (many with memory leaks), printing, etc. (*) http://hub.qgis.org/issues/6383 http://hub.qgis.org/issues/6978 http://hub.qgis.org/issues/7458 http://hub.qgis.org/issues/7940 http://hub.qgis.org/issues/7668 ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer -- Tim Sutton - QGIS Project Steering Committee Member (Release Manager) == Please do not email me off-list with technical support questions. Using the lists will gain more exposure for your issues and the knowledge surrounding your issue will be shared with all. Visit http://linfiniti.com to find out about: * QGIS programming and support services * Mapserver and PostGIS based hosting plans * FOSS Consulting Services Skype: timlinux Irc: timlinux on #qgis at freenode.net == ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] QGIS 2.0 and beyond
Glad to hear you guys will meet on the 2.0 release. In the hope it can help your meeting, I'd like to share my 2 cents as a QGIS evangelist in Southeast Asia. Note, I'm running on QGIS master, so the argument below isn't out of self-interest ;o) In the beginning of March 2013, Tim announced a proposed release schedule over the mailing list [1] which stated June 7, 2012 as date of release. Developers generally agreed around this schedule and process moved forward. In the meantime, QGIS end users and evangelists who keep track of development were left with a general sense of mid-2013 as QGIS 2.0 release, with all its glorious new features and fixes. When doing workshops, presentation on QGIS and discussing about it, by end of June was the best answer I - and surely many other QGIS evangelists praising QGIS out there - could give to people both excited about what's coming. But more importantly, this was a tentative dates when technical limitations and issues would be dealt with when planning forward. For e.g. in Southeast Asia, the broken state of Unicode shapefile encoding in QGIS 1.8 got many people to think twice about adoption. These issues were balanced out with an estimated date of delivery for 2.0 and plans have been drawn for QGIS adoptions in NGOs, ministries, public offices, etc. And this brings us to now. It seems inevitable that QGIS will have to be delayed. IMO, QGIS must insure the delay is as short as possible, to avoid negative impact on current end users expecting new features and issues fixed, as well as not being an obstacle to further adoption by missing an important deadline. Beyond the 80+ blockers currently listed, which could be dealt with in relatively short amount of time and focus, a SIP upgrade proposal is the other main delayer. The argument for a delay to include the SIP upgrade is that, since the needed new vector API broke the plugins, and the SIP upgrade would also break plugins, the two should occur at the same time not to piss off plugin developers with too many breakages along the line. That's a valid argument, no question there, but shouldn’t be the only weighting factor, nor should it open the door to an absence of hard deadlines. I feel that for the SIP upgrade to be considered so late in the release process, it should be considered within _reasonable confines_ to avoid un-managed, harmful delays. Ideally, something along the lines of merged by this coming Sunday or delayed to post 2.0. If the attempt at upgrading SIP is turning out to be more complex and take longer than a hard commit-to-master deadline, it IMO should be postponed on practical grounds of avoiding impact on QGIS end users and adoption. Alright, I don't claim having a perfect understanding of the bigger picture at play here, and I'm not intimately familiar with the source code, so disregard what's not proper. :) Still hope the above point of view, from a person trying to push for more QGIS adoption, can be of help. Regards Mathieu [1] http://lists.osgeo.org/pipermail/qgis-developer/2013-March/024685.html On Mon, Jun 3, 2013 at 4:24 AM, Tim Sutton li...@linfiniti.com wrote: Hi Thanks very much Giovanni. We are holding a PSC meeting tomorrow to plan the release strategy and your revisions will come in handy for that. Regards Tim On Sun, Jun 2, 2013 at 11:30 AM, Giovanni Manghi giovanni.man...@faunalia.pt wrote: Giovanni could you do a triage of the blocker issue queue - it seems like some could be removed (e.g. http://hub.qgis.org/issues/7619 could be closed?). I checked the queue and cleaned it as much as possible. There is a small list of tickets that probably can be closed(*), but the other 71 are pretty much confirmed (almost all regressions). There is a bit of everything, big issues with edit tools, wfs client, ftools (many with memory leaks), printing, etc. (*) http://hub.qgis.org/issues/6383 http://hub.qgis.org/issues/6978 http://hub.qgis.org/issues/7458 http://hub.qgis.org/issues/7940 http://hub.qgis.org/issues/7668 ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer -- Tim Sutton - QGIS Project Steering Committee Member (Release Manager) == Please do not email me off-list with technical support questions. Using the lists will gain more exposure for your issues and the knowledge surrounding your issue will be shared with all. Visit http://linfiniti.com to find out about: * QGIS programming and support services * Mapserver and PostGIS based hosting plans * FOSS Consulting Services Skype: timlinux Irc: timlinux on #qgis at freenode.net == ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] QGIS 2.0 and beyond
On Mon, Jun 3, 2013 at 2:08 PM, Mathieu Pellerin nirvn.a...@gmail.comwrote: I feel that for the SIP upgrade to be considered so late in the release process, it should be considered within _reasonable confines_ to avoid un-managed, harmful delays. Ideally, something along the lines of merged by this coming Sunday or delayed to post 2.0. If the attempt at upgrading SIP is turning out to be more complex and take longer than a hard commit-to-master deadline, it IMO should be postponed on practical grounds of avoiding impact on QGIS end users and adoption. This is the current plan. Victor is working on updating sextante this week, and Alex is working on fTools, noone has put their hands up for the others (DBManger, mapserver export) yet but I will try my hand at them if I get time. The SIP update must happen now or it can't happen in the future without breaking everything yet again, and that will do more damage to the project then some slight breakages in plugins while they update to 2.0. The SIP update is a easy one, for the core code base and plugin authors, and I only have to check one thing with Martin before I will merge it into master (after most of the core plugins are done). - Nathan ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] QGIS 2.0 and beyond
So what's the hard deadline for SIP, this coming weekend? On Mon, Jun 3, 2013 at 11:18 AM, Nathan Woodrow madman...@gmail.com wrote: On Mon, Jun 3, 2013 at 2:08 PM, Mathieu Pellerin nirvn.a...@gmail.comwrote: I feel that for the SIP upgrade to be considered so late in the release process, it should be considered within _reasonable confines_ to avoid un-managed, harmful delays. Ideally, something along the lines of merged by this coming Sunday or delayed to post 2.0. If the attempt at upgrading SIP is turning out to be more complex and take longer than a hard commit-to-master deadline, it IMO should be postponed on practical grounds of avoiding impact on QGIS end users and adoption. This is the current plan. Victor is working on updating sextante this week, and Alex is working on fTools, noone has put their hands up for the others (DBManger, mapserver export) yet but I will try my hand at them if I get time. The SIP update must happen now or it can't happen in the future without breaking everything yet again, and that will do more damage to the project then some slight breakages in plugins while they update to 2.0. The SIP update is a easy one, for the core code base and plugin authors, and I only have to check one thing with Martin before I will merge it into master (after most of the core plugins are done). - Nathan ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] QGIS 2.0 and beyond
On Wed, May 29, 2013 at 10:16 PM, Sandro Santilli s...@keybit.net wrote: Luca, what about taking the responsibility to maintain a stable branch ? I'd also love to see a 1.8.1 coming out :) It is not a bad idea. I'm pretty sure that if QGIS 2.0 will be out soon, it never will be used in production, due to critical bugs (we will wait at least for 2.0.1 or 2.0.2). The only problem is that we use Windows at work and compiling all things is pain, OSGEO4W doesn't release debug libraries ... ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] QGIS 2.0 and beyond
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 30/05/2013 08:02, Luca Manganelli ha scritto: On Wed, May 29, 2013 at 10:16 PM, Sandro Santilli s...@keybit.net mailto:s...@keybit.net wrote: Luca, what about taking the responsibility to maintain a stable branch ? I'd also love to see a 1.8.1 coming out :) It is not a bad idea. I'm pretty sure that if QGIS 2.0 will be out soon, it never will be used in production, due to critical bugs (we will wait at least for 2.0.1 or 2.0.2). As said, I think backporting fixes should really be important for the future of the project, and power users should seriously consider hiring a developer to maintain this. All the best. - -- Paolo Cavallini - Faunalia www.faunalia.eu Full contact details at www.faunalia.eu/pc Nuovi corsi QGIS e PostGIS: http://www.faunalia.it/calendario -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlGnCoIACgkQ/NedwLUzIr6+gACdHDa8zSPSiZfTHDRqx/6g+WKJ pYoAn1ZdEdwc8FTI4rk+6BMwkV0WQtBD =gdfy -END PGP SIGNATURE- ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] QGIS 2.0 and beyond
Hi I agree the release needs to be delayed, but not indefinitely. My impression until now was that the feature freeze was interpreted in a very broad sense. Maybe we could have another period with only bug fixes (so no api improvements or new features coming as usability fixes). Regards, Marco On 28.05.2013 06:57, Tim Sutton wrote: Hi On Mon, May 27, 2013 at 1:02 PM, Paolo Cavallini cavall...@faunalia.it mailto:cavall...@faunalia.it wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 27/05/2013 12:41, Nathan Woodrow ha scritto: Hey all, So what is the current plans for once QGIS 2.0 is released. Are we planning on making minor point releases, or at least weekly builds on a different branch for the major platforms e.g 2.0.1. As 2.0 is going to be a massive release I have no doubt there might be things that pop up after we have it out the door. Do we have provisions to be able to make easy 2.0.1, 2.0.2 releases? I think we should try to do it, if at all possible. Before that, what is the current plans for the QGIS 2.0 release? We are waiting for the last feature from Borys to make its way into master and then we will be feature complete. Once that is the case I will put out a new timetable for getting 2.0 out the door, but you can expect delays from the original anticipated early June release. I see we have a lot of blockers, and new tickets are flocking in. Undoubtedly we will have to release with blockers open or delay the release. Tim All the best. - -- Paolo Cavallini - Faunalia www.faunalia.eu http://www.faunalia.eu Full contact details at www.faunalia.eu/pc http://www.faunalia.eu/pc Nuovi corsi QGIS e PostGIS: http://www.faunalia.it/calendario -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlGjPVEACgkQ/NedwLUzIr4U2ACcDImDY9LMkKDfTOR3+ZCfh4Fo cb8An1hO/q7t0sMBHd/pdIdDlXh5S+Rt =R3jY -END PGP SIGNATURE- ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org mailto:Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer -- Tim Sutton - QGIS Project Steering Committee Member (Release Manager) == Please do not email me off-list with technical support questions. Using the lists will gain more exposure for your issues and the knowledge surrounding your issue will be shared with all. Visit http://linfiniti.com to find out about: * QGIS programming and support services * Mapserver and PostGIS based hosting plans * FOSS Consulting Services Skype: timlinux Irc: timlinux on #qgis at freenode.net http://freenode.net == ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer -- Dr. Marco Hugentobler Sourcepole - Linux Open Source Solutions Weberstrasse 5, CH-8004 Zürich, Switzerland marco.hugentob...@sourcepole.ch http://www.sourcepole.ch Technical Advisor QGIS Project Steering Committee ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] QGIS 2.0 and beyond
Hi! +1 For Marco and Tim Means: two last features should go into the Release : 1. Plugin Manager (already waiting to be merged) 2. SIPv2 (status unknown but would definitely easen the life for the next years if it would be in 2.0) And we should really go into deep feature freeze right now (except the 2 things above) and extend for another 3 Weeks to fix the blockers. Not to forget that I should give the translators at least one week to catch up with translations after string freeze.. Also I would like to relegate translations with less than 30% from the 2.0 Release because I think with less than 30% it would not make any sense to include the translations .. That would currently mean ~ -10 languages. kind regards Werner On Wed, May 29, 2013 at 8:24 AM, Marco Hugentobler marco.hugentob...@sourcepole.ch wrote: Hi I agree the release needs to be delayed, but not indefinitely. My impression until now was that the feature freeze was interpreted in a very broad sense. Maybe we could have another period with only bug fixes (so no api improvements or new features coming as usability fixes). Regards, Marco On 28.05.2013 06:57, Tim Sutton wrote: Hi On Mon, May 27, 2013 at 1:02 PM, Paolo Cavallini cavall...@faunalia.it wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 27/05/2013 12:41, Nathan Woodrow ha scritto: Hey all, So what is the current plans for once QGIS 2.0 is released. Are we planning on making minor point releases, or at least weekly builds on a different branch for the major platforms e.g 2.0.1. As 2.0 is going to be a massive release I have no doubt there might be things that pop up after we have it out the door. Do we have provisions to be able to make easy 2.0.1, 2.0.2 releases? I think we should try to do it, if at all possible. Before that, what is the current plans for the QGIS 2.0 release? We are waiting for the last feature from Borys to make its way into master and then we will be feature complete. Once that is the case I will put out a new timetable for getting 2.0 out the door, but you can expect delays from the original anticipated early June release. I see we have a lot of blockers, and new tickets are flocking in. Undoubtedly we will have to release with blockers open or delay the release. Tim All the best. - -- Paolo Cavallini - Faunalia www.faunalia.eu Full contact details at www.faunalia.eu/pc Nuovi corsi QGIS e PostGIS: http://www.faunalia.it/calendario -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlGjPVEACgkQ/NedwLUzIr4U2ACcDImDY9LMkKDfTOR3+ZCfh4Fo cb8An1hO/q7t0sMBHd/pdIdDlXh5S+Rt =R3jY -END PGP SIGNATURE- ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer -- Tim Sutton - QGIS Project Steering Committee Member (Release Manager) == Please do not email me off-list with technical support questions. Using the lists will gain more exposure for your issues and the knowledge surrounding your issue will be shared with all. Visit http://linfiniti.com to find out about: * QGIS programming and support services * Mapserver and PostGIS based hosting plans * FOSS Consulting Services Skype: timlinux Irc: timlinux on #qgis at freenode.net == ___ Qgis-developer mailing listQgis-developer@lists.osgeo.orghttp://lists.osgeo.org/mailman/listinfo/qgis-developer -- Dr. Marco Hugentobler Sourcepole - Linux Open Source Solutions Weberstrasse 5, CH-8004 Zürich, switzerlandmarco.hugentob...@sourcepole.ch http://www.sourcepole.ch Technical Advisor QGIS Project Steering Committee ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] QGIS 2.0 and beyond
On Tue, May 28, 2013 at 10:29:13PM +0200, Tim Sutton wrote: Hi On Tue, May 28, 2013 at 5:48 PM, Sandro Santilli s...@keybit.net wrote: On Tue, May 28, 2013 at 04:41:24PM +0100, Filipe Dias wrote: I agree with Giovanni. As an end user I'd rather wait a few more months than get an imcomplete version of QGIS 2.0. +1 Also note that there are currently 10 crasher tickets filed against 1.8.0, and even 1 against 1.7.4. And over 100 blockers in the current queue...I don't want to make a buggy release either but I also don't want to put master in perpetual feature freeze while we wait for perfection to make itself apparent. That's why maintainance releases are important. We're only 1 blocker away from a 1.7.5, and 10 blockers away from 1.8.1. --strk; ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] QGIS 2.0 and beyond
Sandro Santilli-2 wrote That's why maintainance releases are important. We're only 1 blocker away from a 1.7.5, and 10 blockers away from 1.8.1. --strk; ___ Qgis-developer mailing list Qgis-developer@.osgeo http://lists.osgeo.org/mailman/listinfo/qgis-developer I totally agree. We've been pushing many new features and changing API is a great step. 2.x branch will be the start for complete switch from arcgis or Mapinfo in some administrations here. We will then need maintenance releases and relative stability. A release every 6 months is fairly enough to me, I have no time to publish more often. Are we able to plan what will justify 3.0? (multithread / data frames - arcgis like? ) Régis -- View this message in context: http://osgeo-org.1560.x6.nabble.com/QGIS-2-0-and-beyond-tp5055919p5056779.html Sent from the Quantum GIS - Developer mailing list archive at Nabble.com. ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] QGIS 2.0 and beyond
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 29/05/2013 17:17, Régis Haubourg ha scritto: I totally agree. We've been pushing many new features and changing API is a great step. 2.x branch will be the start for complete switch from arcgis or Mapinfo in some administrations here. We will then need maintenance releases and relative stability. A release every 6 months is fairly enough to me, I have no time to publish more often. Hi all. What is a blocker? something that prevents users from upgrading to the newer version. IMO we want to get rid of previous versions as soon as possible, when a new one is released. To do so, we must assure users that they can keep on with their work with the latest version, without a need of switching back to the previous one. That's why we adopted the current classification for blockers. And please remember: we are not talking about *perfection* here, as we still have 1k bugs. On the other hand, I think now it's the time for power users to seriously contribute to the solution of their most annoying bugs. The best option is of course hiring a bunch of developers for this. Please also note that in recent times qgis-dev is seriously broken, so very few people are using it regularly (we normally run many courses, all on qgis-dev, but had to switch back since the beginning of the year). Therefore, probably we had less testing than usual. I suggest to put out a beta release after feature freeze for wider testing, possibly followed by the usual RC sequence. I think we have 1M users now, better be more careful than usual not to disrupt their workflow. All the best. - -- Paolo Cavallini - Faunalia www.faunalia.eu Full contact details at www.faunalia.eu/pc Nuovi corsi QGIS e PostGIS: http://www.faunalia.it/calendario -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlGmIAQACgkQ/NedwLUzIr5iBACcDVawOx+jsJlSPaEntJo3AKv5 DdkAn0iuAceu2gR2x6kyDuGa22O62eqQ =wu39 -END PGP SIGNATURE- ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] QGIS 2.0 and beyond
On Wed, May 29, 2013 at 9:16 AM, Werner Macho werner.ma...@gmail.com wrote: Means: two last features should go into the Release : 1. Plugin Manager (already waiting to be merged) OK. 2. SIPv2 (status unknown but would definitely easen the life for the next years if it would be in 2.0) The feature freeze was already postponed for 2 months. We cannot extend it forever, especially waiting for new features not yet implemented and nobody is working on. And we should really go into deep feature freeze right now (except the 2 things above) and extend for another 3 Weeks to fix the blockers. I agree, another 3 weeks to fix blockers and release by the end of June. The next possible release date IMO is the end of September (2 months of holidays + one month to consolidate again). We have currently 85 blockers, about 10 active developers and about 20 days, that means: 85/10/20=0.4 blocker per developer per day. It should be possible to fix one bug in 2 days. Don't forget to set 'assigned to' when you start to work on a blocker. Radim ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] QGIS 2.0 and beyond
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 29/05/2013 18:52, Radim Blazek ha scritto: I agree, another 3 weeks to fix blockers and release by the end of June. The next possible release date IMO is the end of September (2 months of holidays + one month to consolidate again). Agreed. If at all possible, we should do it before the end of June. We have currently 85 blockers, about 10 active developers and about 20 days, that means: Moreover, a thorough screening of tickets may reveal sveral misclassified or duplicate bugs. I did some cleaning just now, more work is needed. I encourage all bug reporters to check the status of their bugs. Thanks. - -- Paolo Cavallini - Faunalia www.faunalia.eu Full contact details at www.faunalia.eu/pc Nuovi corsi QGIS e PostGIS: http://www.faunalia.it/calendario -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlGmNgcACgkQ/NedwLUzIr6wmQCZAZA8Y5Pj+kUvIlzr3gdcOOhJ M/IAoKtUkvfvYM8B8KaOqpnm/faXCtjc =odFW -END PGP SIGNATURE- ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] QGIS 2.0 and beyond
On Wed, May 29, 2013 at 5:34 PM, Paolo Cavallini cavall...@faunalia.itwrote: Hi all. What is a blocker? something that prevents users from upgrading to the newer version. This is why we (in a public organization) are still using 1.7.4, due to a stupid blocker (the famous postgres duplicate primary key bug with split tool) present in 1.8.0 (but not in 1.7.4). The fix was ready month and month ago, but it was only for 2.0 and we never will see a 1.8.0 release. ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] QGIS 2.0 and beyond
On Wed, May 29, 2013 at 08:46:42PM +0200, Luca Manganelli wrote: On Wed, May 29, 2013 at 5:34 PM, Paolo Cavallini cavall...@faunalia.itwrote: Hi all. What is a blocker? something that prevents users from upgrading to the newer version. This is why we (in a public organization) are still using 1.7.4, due to a stupid blocker (the famous postgres duplicate primary key bug with split tool) present in 1.8.0 (but not in 1.7.4). The fix was ready month and month ago, but it was only for 2.0 and we never will see a 1.8.0 release. Luca, what about taking the responsibility to maintain a stable branch ? I'd also love to see a 1.8.1 coming out :) --strk; ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] QGIS 2.0 and beyond
Hi, Undoubtedly we will have to release with blockers please no :) It would be a huge blow to QGIS reputation as there are actually blockers that make QGIS really unusable for any real life job. cheers! -- Giovanni -- ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] QGIS 2.0 and beyond
I agree with Giovanni. As an end user I'd rather wait a few more months than get an imcomplete version of QGIS 2.0. On Tue, May 28, 2013 at 4:37 PM, Giovanni Manghi giovanni.man...@faunalia.pt wrote: Hi, Undoubtedly we will have to release with blockers please no :) It would be a huge blow to QGIS reputation as there are actually blockers that make QGIS really unusable for any real life job. cheers! -- Giovanni -- ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] QGIS 2.0 and beyond
On Tue, May 28, 2013 at 04:41:24PM +0100, Filipe Dias wrote: I agree with Giovanni. As an end user I'd rather wait a few more months than get an imcomplete version of QGIS 2.0. +1 Also note that there are currently 10 crasher tickets filed against 1.8.0, and even 1 against 1.7.4. --strk; On Tue, May 28, 2013 at 4:37 PM, Giovanni Manghi giovanni.man...@faunalia.pt wrote: Hi, Undoubtedly we will have to release with blockers please no :) It would be a huge blow to QGIS reputation as there are actually blockers that make QGIS really unusable for any real life job. cheers! -- Giovanni -- ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] QGIS 2.0 and beyond
+1 No reason to dish out a QGIS version just to comply with deadline, IMHO its better to delay it a bit than to deal with lots of unsatisfied users from bugs and crashes Ing. Antonio Locandro Tegucigalpa, Honduras Need a GPS map for Central America, Asia or South America / Necesitas un mapa GPS para Centro America, Asia o Sur America Date: Tue, 28 May 2013 17:48:28 +0200 From: s...@keybit.net To: filipesd...@gmail.com CC: qgis-developer@lists.osgeo.org; giovanni.man...@faunalia.pt Subject: Re: [Qgis-developer] QGIS 2.0 and beyond On Tue, May 28, 2013 at 04:41:24PM +0100, Filipe Dias wrote: I agree with Giovanni. As an end user I'd rather wait a few more months than get an imcomplete version of QGIS 2.0. +1 Also note that there are currently 10 crasher tickets filed against 1.8.0, and even 1 against 1.7.4. --strk; On Tue, May 28, 2013 at 4:37 PM, Giovanni Manghi giovanni.man...@faunalia.pt wrote: Hi, Undoubtedly we will have to release with blockers please no :) It would be a huge blow to QGIS reputation as there are actually blockers that make QGIS really unusable for any real life job. cheers! -- Giovanni -- ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] QGIS 2.0 and beyond
Hi On Tue, May 28, 2013 at 5:48 PM, Sandro Santilli s...@keybit.net wrote: On Tue, May 28, 2013 at 04:41:24PM +0100, Filipe Dias wrote: I agree with Giovanni. As an end user I'd rather wait a few more months than get an imcomplete version of QGIS 2.0. +1 Also note that there are currently 10 crasher tickets filed against 1.8.0, and even 1 against 1.7.4. And over 100 blockers in the current queue...I don't want to make a buggy release either but I also don't want to put master in perpetual feature freeze while we wait for perfection to make itself apparent. Regards Tim --strk; On Tue, May 28, 2013 at 4:37 PM, Giovanni Manghi giovanni.man...@faunalia.pt wrote: Hi, Undoubtedly we will have to release with blockers please no :) It would be a huge blow to QGIS reputation as there are actually blockers that make QGIS really unusable for any real life job. cheers! -- Giovanni -- ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer -- Tim Sutton - QGIS Project Steering Committee Member (Release Manager) == Please do not email me off-list with technical support questions. Using the lists will gain more exposure for your issues and the knowledge surrounding your issue will be shared with all. Visit http://linfiniti.com to find out about: * QGIS programming and support services * Mapserver and PostGIS based hosting plans * FOSS Consulting Services Skype: timlinux Irc: timlinux on #qgis at freenode.net == ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] QGIS 2.0 and beyond
For me there is mainly one thing (feature) is missing for QGIS 2.0: The upgrade to the new PyQt API (aka. SIP API V2) I would really not want to see a QGIS 2.0 without this update. I really hope, that this is going to be taken care of by someone. We could also look for sponsors to make this more attractive. I remember Martin announced once, that he'll be looking into this again, but I don't know if this is still valid. Apart from this, I agree, that releasing QGIS with blockers is not a good idea, but also remember, that not every bug which is tagged as a blocker necessarily really is a blocker so we might decide to downgrade some. ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] QGIS 2.0 and beyond
Hi On Tue, May 28, 2013 at 5:37 PM, Giovanni Manghi giovanni.man...@faunalia.pt wrote: Hi, Undoubtedly we will have to release with blockers please no :) It would be a huge blow to QGIS reputation as there are actually blockers that make QGIS really unusable for any real life job. ALL the blockers should make QGIS really unusuable, otherwise IMHO they shouldn't be blockers. Many of the items in the blocker list are indeed irritations but I think the blocker list needs to be aggressively pruned of items that aren't actually causing crashes / data corruption or serious inability to use QGIS. As I said to Sandro, and as we discuss with each release, we will need to make compromises - including considering making a release with a known issues list where there are items that we have no strategy in place to deal with them. Regards Tim cheers! -- Giovanni -- ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer -- Tim Sutton - QGIS Project Steering Committee Member (Release Manager) == Please do not email me off-list with technical support questions. Using the lists will gain more exposure for your issues and the knowledge surrounding your issue will be shared with all. Visit http://linfiniti.com to find out about: * QGIS programming and support services * Mapserver and PostGIS based hosting plans * FOSS Consulting Services Skype: timlinux Irc: timlinux on #qgis at freenode.net == ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] QGIS 2.0 and beyond
Hi On Tue, May 28, 2013 at 10:33 PM, Matthias Kuhn matthias.k...@gmx.ch wrote: For me there is mainly one thing (feature) is missing for QGIS 2.0: The upgrade to the new PyQt API (aka. SIP API V2) I would really not want to see a QGIS 2.0 without this update. I really hope, that this is going to be taken care of by someone. If there is a candidate for doing the work I would be happy to delay the release for this. In the absence of a volunteer (or sponsor dev) to do this, I don't think we should discuss if we can reasonably delay the release for this. We could also look for sponsors to make this more attractive. I remember Martin announced once, that he'll be looking into this again, but I don't know if this is still valid. Apart from this, I agree, that releasing QGIS with blockers is not a good idea, but also remember, that not every bug which is tagged as a blocker necessarily really is a blocker so we might decide to downgrade some. Right that is essentially the same as releasing with blockers since we are just reclassifying items in the blocker queue to be non-blockers :-) But seriously yes I agree many items in the queue should not be classified as blockers IMHO. Regards Tim ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer -- Tim Sutton - QGIS Project Steering Committee Member (Release Manager) == Please do not email me off-list with technical support questions. Using the lists will gain more exposure for your issues and the knowledge surrounding your issue will be shared with all. Visit http://linfiniti.com to find out about: * QGIS programming and support services * Mapserver and PostGIS based hosting plans * FOSS Consulting Services Skype: timlinux Irc: timlinux on #qgis at freenode.net == ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] QGIS 2.0 and beyond
Hi, To me - if a feature worked in QGIS 1.8 but fails in 2.0 - esp. if we paid for its development in QGIS 1.8 - then it is also a blocker. How could I otherwise justify our expenses in QGIS to my boss? Well you know - we paid for this feature to be developed - but maybe with the next version it is broken again ... Andreas Am 28.05.2013 22:36, schrieb Tim Sutton: Hi On Tue, May 28, 2013 at 5:37 PM, Giovanni Manghi giovanni.man...@faunalia.pt wrote: Hi, Undoubtedly we will have to release with blockers please no :) It would be a huge blow to QGIS reputation as there are actually blockers that make QGIS really unusable for any real life job. ALL the blockers should make QGIS really unusuable, otherwise IMHO they shouldn't be blockers. Many of the items in the blocker list are indeed irritations but I think the blocker list needs to be aggressively pruned of items that aren't actually causing crashes / data corruption or serious inability to use QGIS. As I said to Sandro, and as we discuss with each release, we will need to make compromises - including considering making a release with a known issues list where there are items that we have no strategy in place to deal with them. Regards Tim cheers! -- Giovanni -- ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer -- Tim Sutton - QGIS Project Steering Committee Member (Release Manager) == Please do not email me off-list with technical support questions. Using the lists will gain more exposure for your issues and the knowledge surrounding your issue will be shared with all. Visit http://linfiniti.com to find out about: * QGIS programming and support services * Mapserver and PostGIS based hosting plans * FOSS Consulting Services Skype: timlinux Irc: timlinux on #qgis at freenode.net == ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] QGIS 2.0 and beyond
Hi Tim, ALL the blockers should make QGIS really unusuable, otherwise IMHO they shouldn't be blockers. Many of the items in the blocker list are indeed irritations but I think the blocker list needs to be aggressively pruned of items that aren't actually causing crashes / data corruption or serious inability to use QGIS. as we agreed in Lyon, a blocker is a regression or a new feature that does not work as expected, this is the way I tried to maintain the tracker. I would agree to eventually downgrade a few about new features that are not perfect, I do not agree to downgrade any regression. Cheers! ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] QGIS 2.0 and beyond
Hi On Tue, May 28, 2013 at 11:14 PM, Giovanni Manghi giovanni.man...@faunalia.pt wrote: Hi Tim, ALL the blockers should make QGIS really unusuable, otherwise IMHO they shouldn't be blockers. Many of the items in the blocker list are indeed irritations but I think the blocker list needs to be aggressively pruned of items that aren't actually causing crashes / data corruption or serious inability to use QGIS. as we agreed in Lyon, a blocker is a regression or a new feature that does not work as expected, this is the way I tried to maintain the tracker. I would agree to eventually downgrade a few about new features that are not perfect, I do not agree to downgrade any regression. Once we have the last two features (new plugin manager and SIP v2 - latter being a little bit in question still for me) in the code base we can embark on a campaign to get the blockers (as curated by Giovanni) closed. However strategically we also need to accommodate the possibility that no fixes may be forthcoming for certain issues, and decide on some e.g. time limit or other criteria for which a blocker can remain in the queue before it should be downgraded. Giovanni could you do a triage of the blocker issue queue - it seems like some could be removed (e.g. http://hub.qgis.org/issues/7619 could be closed?). I just want to clarify that my position is not that I *want* to make a release with blockers, but I also want to avoid that we indefinitely delay the release without a decent plan of action in place of how to deal with the blockers. Regards Tim Cheers! -- Tim Sutton - QGIS Project Steering Committee Member (Release Manager) == Please do not email me off-list with technical support questions. Using the lists will gain more exposure for your issues and the knowledge surrounding your issue will be shared with all. Visit http://linfiniti.com to find out about: * QGIS programming and support services * Mapserver and PostGIS based hosting plans * FOSS Consulting Services Skype: timlinux Irc: timlinux on #qgis at freenode.net == ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] QGIS 2.0 and beyond
Hi Tim, Giovanni could you do a triage of the blocker issue queue - it seems like some could be removed (e.g. http://hub.qgis.org/issues/7619 could be closed?). yes I can, but (full time) not until later *next* week as I'm Cape Verde to give an extensive QGIS training course. cheers! ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] QGIS 2.0 and beyond
Hi On Wed, May 29, 2013 at 12:11 AM, Giovanni Manghi giovanni.man...@faunalia.pt wrote: Hi Tim, Giovanni could you do a triage of the blocker issue queue - it seems like some could be removed (e.g. http://hub.qgis.org/issues/7619 could be closed?). yes I can, but (full time) not until later *next* week as I'm Cape Verde to give an extensive QGIS training course. Thanks Giovanni! Regards Tim cheers! -- Tim Sutton - QGIS Project Steering Committee Member (Release Manager) == Please do not email me off-list with technical support questions. Using the lists will gain more exposure for your issues and the knowledge surrounding your issue will be shared with all. Visit http://linfiniti.com to find out about: * QGIS programming and support services * Mapserver and PostGIS based hosting plans * FOSS Consulting Services Skype: timlinux Irc: timlinux on #qgis at freenode.net == ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] QGIS 2.0 and beyond
As a first step, could we all individually go to the hub and review our blockers to possibly remove some blockers that are not crucial to a 2.0 release or dups of previous reports? That would facilitate Giovanni's job. Also, while ideally a product should be shipped regression-free, this needs to be balanced with a practical need to actually release a product in a timely fashion too. People are - at least in Southeast Asia - expecting a major update of QGIS by mid 2013, and IMO that expectation should be matched as closely as humanly possible. Balancing things out would mean let's not ship QGIS with 100 open blockers, but let's not wait six more months until we reach an elusive 0 blockers :) M On Wed, May 29, 2013 at 5:23 AM, Tim Sutton li...@linfiniti.com wrote: Hi On Wed, May 29, 2013 at 12:11 AM, Giovanni Manghi giovanni.man...@faunalia.pt wrote: Hi Tim, Giovanni could you do a triage of the blocker issue queue - it seems like some could be removed (e.g. http://hub.qgis.org/issues/7619 could be closed?). yes I can, but (full time) not until later *next* week as I'm Cape Verde to give an extensive QGIS training course. Thanks Giovanni! Regards Tim cheers! -- Tim Sutton - QGIS Project Steering Committee Member (Release Manager) == Please do not email me off-list with technical support questions. Using the lists will gain more exposure for your issues and the knowledge surrounding your issue will be shared with all. Visit http://linfiniti.com to find out about: * QGIS programming and support services * Mapserver and PostGIS based hosting plans * FOSS Consulting Services Skype: timlinux Irc: timlinux on #qgis at freenode.net == ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] QGIS 2.0 and beyond
Hey all, So what is the current plans for once QGIS 2.0 is released. Are we planning on making minor point releases, or at least weekly builds on a different branch for the major platforms e.g 2.0.1. As 2.0 is going to be a massive release I have no doubt there might be things that pop up after we have it out the door. Do we have provisions to be able to make easy 2.0.1, 2.0.2 releases? - Nathan ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] QGIS 2.0 and beyond
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 27/05/2013 12:41, Nathan Woodrow ha scritto: Hey all, So what is the current plans for once QGIS 2.0 is released. Are we planning on making minor point releases, or at least weekly builds on a different branch for the major platforms e.g 2.0.1. As 2.0 is going to be a massive release I have no doubt there might be things that pop up after we have it out the door. Do we have provisions to be able to make easy 2.0.1, 2.0.2 releases? I think we should try to do it, if at all possible. Before that, what is the current plans for the QGIS 2.0 release? I see we have a lot of blockers, and new tickets are flocking in. All the best. - -- Paolo Cavallini - Faunalia www.faunalia.eu Full contact details at www.faunalia.eu/pc Nuovi corsi QGIS e PostGIS: http://www.faunalia.it/calendario -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlGjPVEACgkQ/NedwLUzIr4U2ACcDImDY9LMkKDfTOR3+ZCfh4Fo cb8An1hO/q7t0sMBHd/pdIdDlXh5S+Rt =R3jY -END PGP SIGNATURE- ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] QGIS 2.0 and beyond
Hi Nathan, good top open this thread, you are right that bugfixing releases will probably be necessary. Concerning new features, I just point out that I will work and try to focus on improvements and new features described here [0] , if that helps to define roadmap versions: [0] https://docs.google.com/document/d/1u6Tp0QqKdkY65vQ5v94-8WpltcOxWTbQh2ow5tTkQCQ/edit -- View this message in context: http://osgeo-org.1560.x6.nabble.com/QGIS-2-0-and-beyond-tp5055919p5055924.html Sent from the Quantum GIS - Developer mailing list archive at Nabble.com. ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] QGIS 2.0 and beyond
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 27/05/2013 13:04, Régis Haubourg ha scritto: Concerning new features, I just point out that I will work and try to focus on improvements and new features described here [0] , if that helps to define roadmap versions: [0] https://docs.google.com/document/d/1u6Tp0QqKdkY65vQ5v94-8WpltcOxWTbQh2ow5tTkQCQ/edit cool stuff, thanks Régis! all the best. - -- Paolo Cavallini - Faunalia www.faunalia.eu Full contact details at www.faunalia.eu/pc Nuovi corsi QGIS e PostGIS: http://www.faunalia.it/calendario -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlGjQKgACgkQ/NedwLUzIr7SDgCeIOQIMzR7wx4LBWWIG1pB6pOl TAcAmwbQOZCiP7sScGNwSwr3VF65/fgF =CwMu -END PGP SIGNATURE- ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] QGIS 2.0 and beyond
I see we have a lot of blockers, and new tickets are flocking in. and fixes would also need to be tested, and it is time consuming... ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] QGIS 2.0 and beyond
Hi On Mon, May 27, 2013 at 1:02 PM, Paolo Cavallini cavall...@faunalia.it wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 27/05/2013 12:41, Nathan Woodrow ha scritto: Hey all, So what is the current plans for once QGIS 2.0 is released. Are we planning on making minor point releases, or at least weekly builds on a different branch for the major platforms e.g 2.0.1. As 2.0 is going to be a massive release I have no doubt there might be things that pop up after we have it out the door. Do we have provisions to be able to make easy 2.0.1, 2.0.2 releases? I think we should try to do it, if at all possible. Before that, what is the current plans for the QGIS 2.0 release? We are waiting for the last feature from Borys to make its way into master and then we will be feature complete. Once that is the case I will put out a new timetable for getting 2.0 out the door, but you can expect delays from the original anticipated early June release. I see we have a lot of blockers, and new tickets are flocking in. Undoubtedly we will have to release with blockers open or delay the release. Tim All the best. - -- Paolo Cavallini - Faunalia www.faunalia.eu Full contact details at www.faunalia.eu/pc Nuovi corsi QGIS e PostGIS: http://www.faunalia.it/calendario -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlGjPVEACgkQ/NedwLUzIr4U2ACcDImDY9LMkKDfTOR3+ZCfh4Fo cb8An1hO/q7t0sMBHd/pdIdDlXh5S+Rt =R3jY -END PGP SIGNATURE- ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer -- Tim Sutton - QGIS Project Steering Committee Member (Release Manager) == Please do not email me off-list with technical support questions. Using the lists will gain more exposure for your issues and the knowledge surrounding your issue will be shared with all. Visit http://linfiniti.com to find out about: * QGIS programming and support services * Mapserver and PostGIS based hosting plans * FOSS Consulting Services Skype: timlinux Irc: timlinux on #qgis at freenode.net == ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
