[Qgis-developer] r.to.vect issues

Hi all. The module is giving me trouble: * when used in the grass plugin, I get r.to.vect input=asp_recl@a_user output=asp_recl type=area -s Estrazione delle aree in corso ... Module crashed or killed * when used through Processing, the resulting polygonms have plenty of topology errors (double

Re: [Qgis-developer] QEP - Proposal for QGIS 3.0 after 2.14

Hi, On 22/10/2015 18:01, Larry Shaffer wrote: > > > Hmm. You mean put in a QEP tomorrow, and ask the PSC to vote on that > early next week? I would think at least a week of dev community comments > on such a QEP would be warranted, given the very large scope. > > Maybe ask Jürgen and PSC for

Re: [Qgis-developer] QEP - Proposal for QGIS 3.0 after 2.14

Hi, I also like the idea of a list dedicated to plugins and plugin development. On 21/10/2015 12:59, Tom Chadwin wrote: > The potential downside is fragmentation of the users across too many lists - > specifically, would we lose some subscribers to the dev list? Anyway, I'm in > no position to

Re: [Qgis-developer] QEP - Proposal for QGIS 3.0 after 2.14

Hi, On 21/10/2015 17:01, Matthias Kuhn wrote: > The most important thing would probably be to have a working > implementation for > > * PyQt5 > * Python3 > > If it is possible to merge support for this in the current codebase - > just like it's currently possible with Qt5 - we can start to

[Qgis-developer] feature freeze on master lifted

Hi people, the new version was just branched off, the new tar ball[1] was made and packaging can begin and the feature freeze on master is now over. The new version will be announced once packages for some platforms are available. Jürgen [1] http://qgis.org/downloads/qgis-latest.tar.bz2 --

[Qgis-developer] Release count down on website.

Hi, I'm not sure how others feel about it, but I was thinking maybe we should remove or refine the count down to release on the website. Having people hanging off the release count down is IMO a bit annoying as it means people expect it right on that day. Personally I think a date range would

Re: [Qgis-developer] QEP - Proposal for QGIS 3.0 after 2.14

As Jürgen said, it's essentially the same. Yet... :) I also think branching off 2.14 LTR now is slightly preferable. On a psychological level, as the heavy development of new features has in the past mostly taken place on the master branch, it'd make it clearer to devs that the heavy feature

Re: [Qgis-developer] QEP - Proposal for QGIS 3.0 after 2.14

Hi, On Thu, 22. Oct 2015 at 08:47:26 +1100, Nyall Dawson wrote: > Why not: - Branch off a qt5 branch from master now and start with porting - continue as usual with master to produce 2.14 - branch 2.14 off and release it in four month - then merge the qt5 branch into master (aka 2.15) - finally

Re: [Qgis-developer] QEP - Proposal for QGIS 3.0 after 2.14

On 24 October 2015 at 07:26, Jürgen E. wrote: > Hi, > > On Thu, 22. Oct 2015 at 08:47:26 +1100, Nyall Dawson wrote: >> Why not: > > - Branch off a qt5 branch from master now and start with porting > - continue as usual with master to produce 2.14 > - branch 2.14 off and release it