Hi Régis,
On 19/01/2016 20:54, Régis Haubourg wrote:
>
> hey, we have a QEP process running around labeling / callout lines / saving
> ressources with qgs / porting easycustom labeling and mask plugin to core
> equivalent.
>
> We can target 3.0, there is no hurry, as no coding work has been don
On 19/01/2016 15:25, Paolo Cavallini wrote:
> Il 19/01/2016 14:12, Neumann, Andreas ha scritto:
>> Hi,
>>
>> QGIS is now used by a lot of professional users worldwide. A lot of them
> ...
>> Hugos suggestion to have 2.16 as the LT release instead of 2.14 would
>> also be fine and acceptable for me.
Il 20/01/2016 08:14, Neumann, Andreas ha scritto:
> Sure - makes sense to close those old bugs.
agreed - just make sure they are not valid for later versions.
thanks Nyall!
--
Paolo Cavallini - www.faunalia.eu
QGIS & PostGIS courses: http://www.faunalia.eu/training.html
_
Sure - makes sense to close those old bugs.
Andreas
On 2016-01-20 07:16, Nyall Dawson wrote:
> On 20 Jan 2016 5:15 PM, "Nyall Dawson" wrote:
>>
>> Just wondering,
>>
>> Can I close a the bugs reports related to project file compatibility with
>> versions <2.0? No one is going to addres
On 20 Jan 2016 5:15 PM, "Nyall Dawson" wrote:
>
> Just wondering,
>
> Can I close a the bugs reports related to project file compatibility with
versions <2.0? No one is going to address these now, its just noise on the
tracker...
Oops, that was supposed to be "ALL" the bugs.
>
> Nyall
__
Just wondering,
Can I close a the bugs reports related to project file compatibility with
versions <2.0? No one is going to address these now, its just noise on the
tracker...
Nyall
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List inf
+1 to 2.16 and then 3.0
On Tue, 19 Jan 2016 11:26 pm Martin Dobias wrote:
> On Sun, Jan 17, 2016 at 11:38 PM, Nyall Dawson
> wrote:
> > On 18 January 2016 at 09:03, Tim Sutton wrote:
> >>
> >> Dear QGIS Developers
> >>
> >>
> >> For some time now we have been talking about moving to 3.0. The P
Dear list
I am using OSGeo4W installer in Windows. QGIS master shows that it uses
Gdal/OGR 1.11.3
But when I try OSGeo4W shell, it shows Gdal/ogr 2.0.0dev release.
I can read Spatilaite in QGIS and older version of GDAL/OGR but in the
OSGeo4w shell it comes up with an error saying that GD
Paolo Cavallini wrote
> Il 19/01/2016 14:12, Neumann, Andreas ha scritto:
>> Hi,
>>
>> QGIS is now used by a lot of professional users worldwide. A lot of them
> ...
>> Hugos suggestion to have 2.16 as the LT release instead of 2.14 would
>> also be fine and acceptable for me. Moving to 3.0 immedi
On 19-01-16 11:59, Matthias Kuhn wrote:
> Hi Richard,
>
> Based on geoserver autobuild scripts I implemented this:
>
> https://github.com/QGEP/docs/blob/master/.travis.yml
Thanks Matthias,
Based on your example and some reading I managed to get our docs building.
Currently only master and html
killed and restarted, it should be fine now.
2016-01-19 15:32 GMT+01:00 Alessandro Pasotti :
> load average: 10.82, 10.75, 10.78
>
>
> 2016-01-19 15:31 GMT+01:00 Paolo Cavallini :
>
>> Hi all,
>> the Django app has suddenly become far slower, and I now got:
>> 504 Gateway Time-out
>> nginx/1.4.7
Il 19/01/2016 15:35, Alessandro Pasotti ha scritto:
> killed and restarted, it should be fine now.
confirmed, thanks
--
Paolo Cavallini - www.faunalia.eu
QGIS & PostGIS courses: http://www.faunalia.eu/training.html
___
Qgis-developer mailing list
Qgis-
load average: 10.82, 10.75, 10.78
2016-01-19 15:31 GMT+01:00 Paolo Cavallini :
> Hi all,
> the Django app has suddenly become far slower, and I now got:
> 504 Gateway Time-out
> nginx/1.4.7
> Any explanation/fix?
> Thanks.
> --
> Paolo Cavallini - www.faunalia.eu
> QGIS & PostGIS courses: http:/
Hi all,
the Django app has suddenly become far slower, and I now got:
504 Gateway Time-out
nginx/1.4.7
Any explanation/fix?
Thanks.
--
Paolo Cavallini - www.faunalia.eu
QGIS & PostGIS courses: http://www.faunalia.eu/training.html
___
Qgis-developer maili
Il 19/01/2016 14:12, Neumann, Andreas ha scritto:
> Hi,
>
> QGIS is now used by a lot of professional users worldwide. A lot of them
...
> Hugos suggestion to have 2.16 as the LT release instead of 2.14 would
> also be fine and acceptable for me. Moving to 3.0 immediately would not
> work well for
+1 with Andreas, the very same analysis here.
Cheers all,
Régis
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/Help-us-plan-for-QGIS-3-0-tp5245740p5246088.html
Sent from the Quantum GIS - Developer mailing list archive at Nabble.com.
_
On Sun, Jan 17, 2016 at 11:38 PM, Nyall Dawson wrote:
> On 18 January 2016 at 09:03, Tim Sutton wrote:
>>
>> Dear QGIS Developers
>>
>>
>> For some time now we have been talking about moving to 3.0. The PSC is
>> looking for proposals on how to manage the process of moving to QGIS 3.0.
>> For a
Hi,
QGIS is now used by a lot of professional users worldwide. A lot of them
have contracts with QGIS developes/companies and expect that they can be
delivered within a few months. If we move now to QGIS 3.0 on such short
notice, without any concrete plan/warning, means such projects can only
On 19-01-16 10:48, Yves Jacolin wrote:
> On Tuesday, January 19, 2016 20:44:25 Nyall Dawson wrote:
>> Hi all (Tim?)
>>
>> Can we put out a call for 2.14 beta testers on the blog/social media
>> accounts?
>>
>> Will be good to get as much feedback pre LTS release as possible.
>>
>> Nyall
> Nyal, All
Hmm. Not at all usable, I'm afraid. I would have thought a properly
documented changelog for releases would be A Good Thing.
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/Point-minor-release-changelogs-tp5246035p5246069.html
Sent from the Quantum GIS - Developer mailing l
On Tue, Jan 19, 2016 at 11:23 AM, Richard Duivenvoorde
wrote:
>
>
> I think 'we' should even create a post on blog.qgis.org for every even
> minor upgrades
>
>
I've published a short announcement now.
Best wishes,
Anita
___
Qgis-developer mailing
On 19-01-16 12:50, Anita Graser wrote:
> Nathan has admin rights and I do. Maybe we can create a generic admin
> account or just give all PSC members admin rights. I can't share my
> login since it also works for my private blog.
Yes, that is what I'm proposing. You could for example use
ad...@qg
>
>
> O
> n Tue, 19 Jan 2016 8:05 pm Richard Duivenvoorde
> wrote:
>
>>
>>
>> We have blog.qgis.org (a wordpress site). If you provide me some text
>> (and maybe image) I'm happy to put it on the 'offical' blog.
>> Anita can maybe give you a login to do it yourself if you prefer?
>> @Anita: can
On 19-01-16 11:51, Tom Chadwin wrote:
> No, I don't mean announcing that the releases are available - I mean a
> changelog for the releases. Where is that?
It is added to the 'ChangeLog' file in the Release 2.y.z commit:
https://github.com/qgis/QGIS/commit/e72e2abd0e22ca414af5268dff27c8dce84dc523
Should tickets with Resolution set to up/downstream remain
in state "Open" until the bug is fixed up/downstream ?
Or "Feedback" or "Closed" ?
I've closed http://hub.qgis.org/issues/11900 but then found
other cases in which the ticket was left open, like this:
http://hub.qgis.org/issues/12935
So,
On Tuesday, January 19, 2016 11:31:38 Richard Duivenvoorde wrote:
> Hi Dev's,
>
> Any Travis guru's here have some time to help the doc team/me to move
> the building of the docs to Travis, so we can also have this cool
> build/passing icons :-)
>
> No seriously: the doc team is getting on steam
Oops, mapserver I wanted to say, shame on me.
On 01/19/2016 11:59 AM, Matthias Kuhn wrote:
> Hi Richard,
>
> Based on geoserver autobuild scripts I implemented this:
>
> https://github.com/QGEP/docs/blob/master/.travis.yml
>
> Bests,
> Matthias
>
> On 01/19/2016 11:31 AM, Richard Duivenvoorde wrot
On Tuesday, January 19, 2016 20:44:25 Nyall Dawson wrote:
> Hi all (Tim?)
>
> Can we put out a call for 2.14 beta testers on the blog/social media
> accounts?
>
> Will be good to get as much feedback pre LTS release as possible.
>
> Nyall
Nyal, All,
In order to help power users to test the futu
No, I don't mean announcing that the releases are available - I mean a
changelog for the releases. Where is that?
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/Point-minor-release-changelogs-tp5246035p5246052.html
Sent from the Quantum GIS - Developer mailing list archive
Hi Richard,
Based on geoserver autobuild scripts I implemented this:
https://github.com/QGEP/docs/blob/master/.travis.yml
Bests,
Matthias
On 01/19/2016 11:31 AM, Richard Duivenvoorde wrote:
> Hi Dev's,
>
> Any Travis guru's here have some time to help the doc team/me to move
> the building of t
Hi,
On 19/01/2016 11:08, Paolo Cavallini wrote:
> Il 19/01/2016 10:38, Richard Duivenvoorde ha scritto:
>> On 17-01-16 23:03, Tim Sutton wrote:
>>> [1] http://blog.qgis.org/2016/01/17/help-us-to-plan-for-qgis-3-0/
>>
>> Dev's,
>>
>> Nobody else?
>
> My suggestion:
> * release 2.14 LTR
> * move im
Hi Dev's,
Any Travis guru's here have some time to help the doc team/me to move
the building of the docs to Travis, so we can also have this cool
build/passing icons :-)
No seriously: the doc team is getting on steam to do a big documentation
update for 2.14 LTR docs.
And to be sure (with a lot o
On 19-01-16 11:04, Tom Chadwin wrote:
> I try to keep the users within the organizations I work with aware of new
> versions of QGIS when they are released. I also like to summarize some of
> the changes. My Google skills are failing me, however, in finding changelogs
> for eg 2.8.6 and 2.12.3, rat
I try to keep the users within the organizations I work with aware of new
versions of QGIS when they are released. I also like to summarize some of
the changes. My Google skills are failing me, however, in finding changelogs
for eg 2.8.6 and 2.12.3, rather than for 2.8 and 2.12. I'm sure I've found
Hey Richard,
Yes I can share the password. I will send it though.
Regards
On Tue, 19 Jan 2016 8:05 pm Richard Duivenvoorde
wrote:
> On 19-01-16 10:44, Nyall Dawson wrote:
> > Hi all (Tim?)
> >
> > Can we put out a call for 2.14 beta testers on the blog/social media
> > accounts?
> >
> > Will be
Il 19/01/2016 10:38, Richard Duivenvoorde ha scritto:
> On 17-01-16 23:03, Tim Sutton wrote:
>> [1] http://blog.qgis.org/2016/01/17/help-us-to-plan-for-qgis-3-0/
>
> Dev's,
>
> Nobody else?
My suggestion:
* release 2.14 LTR
* move immediately to 3.0
* backport all fixes to 2.14, as usual for LTR
On 19-01-16 10:44, Nyall Dawson wrote:
> Hi all (Tim?)
>
> Can we put out a call for 2.14 beta testers on the blog/social media
> accounts?
>
> Will be good to get as much feedback pre LTS release as possible.
Hi Nyall,
We have blog.qgis.org (a wordpress site). If you provide me some text
(and
I just thought I'd reassure you that the discussion is being read and not
ignored. As just a plugin dev, I cannot offer any opinion - the core devs
will come to the best consensus, and the rest of us can all then work at
fixing our plugins.
--
View this message in context:
http://osgeo-org.1560
Il 19/01/2016 10:44, Nyall Dawson ha scritto:
> Hi all (Tim?)
>
> Can we put out a call for 2.14 beta testers on the blog/social media
> accounts?
>
> Will be good to get as much feedback pre LTS release as possible.
+1 from me - good idea.
Thanks Nyall.
--
Paolo Cavallini - www.faunalia.eu
QG
Hi all,
I just proposed a PR for fixing this issue :
https://github.com/qgis/QGIS/pull/2696
related to
http://hub.qgis.org/issues/14110
Thanks for review and merge.
2016-01-15 11:29 GMT+01:00 kimaidou :
> Hi all,
>
> Some users reported a bug in DbManager. When you connect to a database,
> and
Hi all (Tim?)
Can we put out a call for 2.14 beta testers on the blog/social media
accounts?
Will be good to get as much feedback pre LTS release as possible.
Nyall
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.
On 17-01-16 23:03, Tim Sutton wrote:
> Dear QGIS Developers
>
>
> For some time now we have been talking about moving to 3.0. The PSC is
> looking for proposals on how to manage the process of moving to QGIS
> 3.0. For a little more context please see the blog post I have made [1].
> Once we have
42 matches
Mail list logo
