Re: [QGIS-Developer] What to do about GDAL and PROJ for 3.10.2?

[Mathieu Pellerin]

Great news, best way to open 2020 :)

On Thu, Dec 19, 2019, 14:14 Kristian Evers  wrote:

>
>
> On 19 Dec 2019, at 03:37, Mathieu Pellerin  wrote:
>
> Having helped out chasing down some of these CRS and transformation issues
> under GDAL3/PROJ6, I too feel *very* uncomfortable shipping the next QGIS
> point release with anything lesser than GDAL3 and PROJ6 master as of
> yesterday.
>
> To be clear, QGIS had plenty to fix itself, and that’s been taken care of
> (thanks to QGIS’s PSC for financing Nyall here). But those fixes are half
> of the story, and if we are to ship a QGIS version built against
> GDAL3/PROJ6 that can be trusted to project and transform data properly, we
> can’t do so unless we ship with the latest revisions of those libraries.
>
> On the short term, since the next point release is in 24-ish hours, I’d
> suggest to update the osgeo4w gdal and proj non-dev libraries to the latest
> master revisions (with versions like proj6 version 6.3pre or something) and
> have QGIS 3.10.2 built against those. Jürgen, since you’d carry that
> library update burden, how do you feel about this solution?
>
> Following that, we should discuss with GDAL and PROJ to see if they can
> package an official release prior to QGIS’ next point release (which is to
> take place on January 17, 2019 according to our schedule). Once that’s
> done, we should consider raising QGIS’ minimum version requirement for
> those libraries.
>
>
> PROJ 6.3.0 is scheduled for release January 1st.
>
> Math
>
> On Thu, Dec 19, 2019 at 8:30 AM Nyall Dawson 
> wrote:
>
>> Hi list,
>>
>> Just want to raise this discussion prior to the 3.10.2 patch release.
>> The situation as I see it is that there is absolutely critical fixes
>> in GDAL and PROJ master branches which are not available in any of the
>> GDAL/PROJ stable releases, all relating to CRS and transformation
>> handling.
>>
>> Many of these fixes have been implemented as a direct result of bug
>> reports filed against QGIS when running under the Proj6/GDAL3
>> combination.
>>
>> I personally do not feel comfortable with anyone running QGIS on
>> GDAL3/Proj6 without these fixes (in fact, I think that we should block
>> QGIS builds on GDAL/PROJ builds less than master, and greater than
>> PROJ 5/ GDAL 2 via cmake checks). So we're left in a difficult
>> position, because the next round of GDAL/PROJ releases aren't
>> happening anytime soon.
>>
>> Thoughts welcome on how we should proceed here
>>
>> Nyall
>> ___
>> QGIS-Developer mailing list
>> QGIS-Developer@lists.osgeo.org
>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>
>
>
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] What to do about GDAL and PROJ for 3.10.2?

[Kristian Evers]

On 19 Dec 2019, at 03:37, Mathieu Pellerin 
mailto:nirvn.a...@gmail.com>> wrote:

Having helped out chasing down some of these CRS and transformation issues 
under GDAL3/PROJ6, I too feel *very* uncomfortable shipping the next QGIS point 
release with anything lesser than GDAL3 and PROJ6 master as of yesterday.

To be clear, QGIS had plenty to fix itself, and that’s been taken care of 
(thanks to QGIS’s PSC for financing Nyall here). But those fixes are half of 
the story, and if we are to ship a QGIS version built against GDAL3/PROJ6 that 
can be trusted to project and transform data properly, we can’t do so unless we 
ship with the latest revisions of those libraries.

On the short term, since the next point release is in 24-ish hours, I’d suggest 
to update the osgeo4w gdal and proj non-dev libraries to the latest master 
revisions (with versions like proj6 version 6.3pre or something) and have QGIS 
3.10.2 built against those. Jürgen, since you’d carry that library update 
burden, how do you feel about this solution?

Following that, we should discuss with GDAL and PROJ to see if they can package 
an official release prior to QGIS’ next point release (which is to take place 
on January 17, 2019 according to our schedule). Once that’s done, we should 
consider raising QGIS’ minimum version requirement for those libraries.


PROJ 6.3.0 is scheduled for release January 1st.

Math

On Thu, Dec 19, 2019 at 8:30 AM Nyall Dawson 
mailto:nyall.daw...@gmail.com>> wrote:
Hi list,

Just want to raise this discussion prior to the 3.10.2 patch release.
The situation as I see it is that there is absolutely critical fixes
in GDAL and PROJ master branches which are not available in any of the
GDAL/PROJ stable releases, all relating to CRS and transformation
handling.

Many of these fixes have been implemented as a direct result of bug
reports filed against QGIS when running under the Proj6/GDAL3
combination.

I personally do not feel comfortable with anyone running QGIS on
GDAL3/Proj6 without these fixes (in fact, I think that we should block
QGIS builds on GDAL/PROJ builds less than master, and greater than
PROJ 5/ GDAL 2 via cmake checks). So we're left in a difficult
position, because the next round of GDAL/PROJ releases aren't
happening anytime soon.

Thoughts welcome on how we should proceed here

Nyall
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] What to do about GDAL and PROJ for 3.10.2?

[Paolo Cavallini]

Hi again,

Il 19/12/19 07:57, Nyall Dawson ha scritto:
> On Thu, 19 Dec 2019 at 16:51, Paolo Cavallini  wrote:
>>
>> Hi Nyall,
>> thanks for clarifying this. Wouldn't it be reasonable to ask gdal+proj
>> teams to release a new fixed version ASAP? Even if we fix this in the
>> Windows installer, where we (Juergen) have full control, we'll still
>> have issues on other OSs where we cannot control dependencies.
> 
> We can, but I don't honestly see that happening before Christmas (it
> is the holiday season after all!)
In this case I don't see a major problem in postponing a point release,
or even skipping it until the next one - am I wrong?
Cheers.
-- 
Paolo Cavallini - www.faunalia.eu
QGIS.ORG Chair:
http://planet.qgis.org/planet/user/28/tag/qgis%20board/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] What to do about GDAL and PROJ for 3.10.2?

[Nyall Dawson]

On Thu, 19 Dec 2019 at 16:51, Paolo Cavallini  wrote:
>
> Hi Nyall,
> thanks for clarifying this. Wouldn't it be reasonable to ask gdal+proj
> teams to release a new fixed version ASAP? Even if we fix this in the
> Windows installer, where we (Juergen) have full control, we'll still
> have issues on other OSs where we cannot control dependencies.

We can, but I don't honestly see that happening before Christmas (it
is the holiday season after all!)

Nyall

> Cheers.
>
> Il 19/12/19 03:37, Mathieu Pellerin ha scritto:
> > Having helped out chasing down some of these CRS and transformation
> > issues under GDAL3/PROJ6, I too feel *very* uncomfortable shipping the
> > next QGIS point release with anything lesser than GDAL3 and PROJ6 master
> > as of yesterday.
> >
> > To be clear, QGIS had plenty to fix itself, and that’s been taken care
> > of (thanks to QGIS’s PSC for financing Nyall here). But those fixes are
> > half of the story, and if we are to ship a QGIS version built against
> > GDAL3/PROJ6 that can be trusted to project and transform data properly,
> > we can’t do so unless we ship with the latest revisions of those libraries.
> >
> > On the short term, since the next point release is in 24-ish hours, I’d
> > suggest to update the osgeo4w gdal and proj non-dev libraries to the
> > latest master revisions (with versions like proj6 version 6.3pre or
> > something) and have QGIS 3.10.2 built against those. Jürgen, since you’d
> > carry that library update burden, how do you feel about this solution?
> >
> > Following that, we should discuss with GDAL and PROJ to see if they can
> > package an official release prior to QGIS’ next point release (which is
> > to take place on January 17, 2019 according to our schedule). Once
> > that’s done, we should consider raising QGIS’ minimum version
> > requirement for those libraries.
> >
> > Math
> >
> > On Thu, Dec 19, 2019 at 8:30 AM Nyall Dawson  > > wrote:
> >
> > Hi list,
> >
> > Just want to raise this discussion prior to the 3.10.2 patch release.
> > The situation as I see it is that there is absolutely critical fixes
> > in GDAL and PROJ master branches which are not available in any of the
> > GDAL/PROJ stable releases, all relating to CRS and transformation
> > handling.
> >
> > Many of these fixes have been implemented as a direct result of bug
> > reports filed against QGIS when running under the Proj6/GDAL3
> > combination.
> >
> > I personally do not feel comfortable with anyone running QGIS on
> > GDAL3/Proj6 without these fixes (in fact, I think that we should block
> > QGIS builds on GDAL/PROJ builds less than master, and greater than
> > PROJ 5/ GDAL 2 via cmake checks). So we're left in a difficult
> > position, because the next round of GDAL/PROJ releases aren't
> > happening anytime soon.
> >
> > Thoughts welcome on how we should proceed here
> >
> > Nyall
> > ___
> > QGIS-Developer mailing list
> > QGIS-Developer@lists.osgeo.org 
> > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> >
> >
> > ___
> > QGIS-Developer mailing list
> > QGIS-Developer@lists.osgeo.org
> > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> >
>
> --
> Paolo Cavallini - www.faunalia.eu
> QGIS.ORG Chair:
> http://planet.qgis.org/planet/user/28/tag/qgis%20board/
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] What to do about GDAL and PROJ for 3.10.2?

[Paolo Cavallini]

Hi Nyall,
thanks for clarifying this. Wouldn't it be reasonable to ask gdal+proj
teams to release a new fixed version ASAP? Even if we fix this in the
Windows installer, where we (Juergen) have full control, we'll still
have issues on other OSs where we cannot control dependencies.
Cheers.

Il 19/12/19 03:37, Mathieu Pellerin ha scritto:
> Having helped out chasing down some of these CRS and transformation
> issues under GDAL3/PROJ6, I too feel *very* uncomfortable shipping the
> next QGIS point release with anything lesser than GDAL3 and PROJ6 master
> as of yesterday.
> 
> To be clear, QGIS had plenty to fix itself, and that’s been taken care
> of (thanks to QGIS’s PSC for financing Nyall here). But those fixes are
> half of the story, and if we are to ship a QGIS version built against
> GDAL3/PROJ6 that can be trusted to project and transform data properly,
> we can’t do so unless we ship with the latest revisions of those libraries.
> 
> On the short term, since the next point release is in 24-ish hours, I’d
> suggest to update the osgeo4w gdal and proj non-dev libraries to the
> latest master revisions (with versions like proj6 version 6.3pre or
> something) and have QGIS 3.10.2 built against those. Jürgen, since you’d
> carry that library update burden, how do you feel about this solution?
> 
> Following that, we should discuss with GDAL and PROJ to see if they can
> package an official release prior to QGIS’ next point release (which is
> to take place on January 17, 2019 according to our schedule). Once
> that’s done, we should consider raising QGIS’ minimum version
> requirement for those libraries.
> 
> Math
> 
> On Thu, Dec 19, 2019 at 8:30 AM Nyall Dawson  > wrote:
> 
> Hi list,
> 
> Just want to raise this discussion prior to the 3.10.2 patch release.
> The situation as I see it is that there is absolutely critical fixes
> in GDAL and PROJ master branches which are not available in any of the
> GDAL/PROJ stable releases, all relating to CRS and transformation
> handling.
> 
> Many of these fixes have been implemented as a direct result of bug
> reports filed against QGIS when running under the Proj6/GDAL3
> combination.
> 
> I personally do not feel comfortable with anyone running QGIS on
> GDAL3/Proj6 without these fixes (in fact, I think that we should block
> QGIS builds on GDAL/PROJ builds less than master, and greater than
> PROJ 5/ GDAL 2 via cmake checks). So we're left in a difficult
> position, because the next round of GDAL/PROJ releases aren't
> happening anytime soon.
> 
> Thoughts welcome on how we should proceed here
> 
> Nyall
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org 
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> 
> 
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> 

-- 
Paolo Cavallini - www.faunalia.eu
QGIS.ORG Chair:
http://planet.qgis.org/planet/user/28/tag/qgis%20board/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] What to do about GDAL and PROJ for 3.10.2?

[Nyall Dawson]

On Thu, 19 Dec 2019 at 12:37, Mathieu Pellerin  wrote:

> To be clear, QGIS had plenty to fix itself, and that’s been taken care of 
> (thanks to QGIS’s PSC for financing Nyall here).

s/been/being/
;)

Nyall
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] What to do about GDAL and PROJ for 3.10.2?

[Mathieu Pellerin]

Having helped out chasing down some of these CRS and transformation issues
under GDAL3/PROJ6, I too feel *very* uncomfortable shipping the next QGIS
point release with anything lesser than GDAL3 and PROJ6 master as of
yesterday.

To be clear, QGIS had plenty to fix itself, and that’s been taken care of
(thanks to QGIS’s PSC for financing Nyall here). But those fixes are half
of the story, and if we are to ship a QGIS version built against
GDAL3/PROJ6 that can be trusted to project and transform data properly, we
can’t do so unless we ship with the latest revisions of those libraries.

On the short term, since the next point release is in 24-ish hours, I’d
suggest to update the osgeo4w gdal and proj non-dev libraries to the latest
master revisions (with versions like proj6 version 6.3pre or something) and
have QGIS 3.10.2 built against those. Jürgen, since you’d carry that
library update burden, how do you feel about this solution?

Following that, we should discuss with GDAL and PROJ to see if they can
package an official release prior to QGIS’ next point release (which is to
take place on January 17, 2019 according to our schedule). Once that’s
done, we should consider raising QGIS’ minimum version requirement for
those libraries.

Math

On Thu, Dec 19, 2019 at 8:30 AM Nyall Dawson  wrote:

> Hi list,
>
> Just want to raise this discussion prior to the 3.10.2 patch release.
> The situation as I see it is that there is absolutely critical fixes
> in GDAL and PROJ master branches which are not available in any of the
> GDAL/PROJ stable releases, all relating to CRS and transformation
> handling.
>
> Many of these fixes have been implemented as a direct result of bug
> reports filed against QGIS when running under the Proj6/GDAL3
> combination.
>
> I personally do not feel comfortable with anyone running QGIS on
> GDAL3/Proj6 without these fixes (in fact, I think that we should block
> QGIS builds on GDAL/PROJ builds less than master, and greater than
> PROJ 5/ GDAL 2 via cmake checks). So we're left in a difficult
> position, because the next round of GDAL/PROJ releases aren't
> happening anytime soon.
>
> Thoughts welcome on how we should proceed here
>
> Nyall
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] What to do about GDAL and PROJ for 3.10.2?

[Nyall Dawson]

Hi list,

Just want to raise this discussion prior to the 3.10.2 patch release.
The situation as I see it is that there is absolutely critical fixes
in GDAL and PROJ master branches which are not available in any of the
GDAL/PROJ stable releases, all relating to CRS and transformation
handling.

Many of these fixes have been implemented as a direct result of bug
reports filed against QGIS when running under the Proj6/GDAL3
combination.

I personally do not feel comfortable with anyone running QGIS on
GDAL3/Proj6 without these fixes (in fact, I think that we should block
QGIS builds on GDAL/PROJ builds less than master, and greater than
PROJ 5/ GDAL 2 via cmake checks). So we're left in a difficult
position, because the next round of GDAL/PROJ releases aren't
happening anytime soon.

Thoughts welcome on how we should proceed here

Nyall
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] Plugin [1902] Azure Maps approval notification.

[noreply]

Plugin Azure Maps approval by pcav.
The plugin version "[1902] Azure Maps 0.5 Experimental" is now approved
Link: http://plugins.qgis.org/plugins/QGISPlugin/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Plugin [1905] Deactivate Active Labels approval notification.

[Osahon Oduware]

THE TRUTH CANNOT BE HIDDEN
**Explosion in my car.
https://www.docdroid.net/s11XHOS/the-truth-cannot-be-hidden.pdf

On Wed, 18 Dec 2019, 18:57 ,  wrote:

>
> Plugin Deactivate Active Labels approval by pcav.
> The plugin version "[1905] Deactivate Active Labels 0.5" is now approved
> Link: http://plugins.qgis.org/plugins/deactivate_active_labels/
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] Plugin [1905] Deactivate Active Labels approval notification.

[noreply]

Plugin Deactivate Active Labels approval by pcav.
The plugin version "[1905] Deactivate Active Labels 0.4" is now approved
Link: http://plugins.qgis.org/plugins/deactivate_active_labels/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] Plugin [1905] Deactivate Active Labels approval notification.

[noreply]

Plugin Deactivate Active Labels approval by pcav.
The plugin version "[1905] Deactivate Active Labels 0.2" is now approved
Link: http://plugins.qgis.org/plugins/deactivate_active_labels/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] Plugin [1905] Deactivate Active Labels approval notification.

[noreply]

Plugin Deactivate Active Labels approval by pcav.
The plugin version "[1905] Deactivate Active Labels 0.5" is now approved
Link: http://plugins.qgis.org/plugins/deactivate_active_labels/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] Plugin [1905] Deactivate Active Labels approval notification.

[noreply]

Plugin Deactivate Active Labels approval by pcav.
The plugin version "[1905] Deactivate Active Labels 0.3" is now approved
Link: http://plugins.qgis.org/plugins/deactivate_active_labels/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] Plugin [1905] Deactivate Active Labels approval notification.

[noreply]

Plugin Deactivate Active Labels approval by pcav.
The plugin version "[1905] Deactivate Active Labels 0.1" is now approved
Link: http://plugins.qgis.org/plugins/deactivate_active_labels/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] Plugin [1153] VDL Tools approval notification.

[noreply]

Plugin VDL Tools approval by pcav.
The plugin version "[1153] VDL Tools 0.8 Experimental" is now approved
Link: http://plugins.qgis.org/plugins/VDLTools/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] Plugin [1880] Guided Offline Editing approval notification.

[noreply]

Plugin Guided Offline Editing approval by pcav.
The plugin version "[1880] Guided Offline Editing 0.5.1 Experimental" is now 
approved
Link: http://plugins.qgis.org/plugins/guided_offline_editing/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] Plugin [1913] CSV Tools approval notification.

[noreply]

Plugin CSV Tools approval by pcav.
The plugin version "[1913] CSV Tools 0.4.1 Experimental" is now approved
Link: http://plugins.qgis.org/plugins/csv_tools/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] Plugin [995] dzetsaka : Classification tool approval notification.

[noreply]

Plugin dzetsaka : Classification tool approval by pcav.
The plugin version "[995] dzetsaka : Classification tool 3.61" is now approved
Link: http://plugins.qgis.org/plugins/dzetsaka/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] Plugin [1909] EZPrinter approval notification.

[noreply]

Plugin EZPrinter approval by pcav.
The plugin version "[1909] EZPrinter 0.2" is now approved
Link: http://plugins.qgis.org/plugins/ezprinter/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Improve build times with ccache

[Etienne Trimaille]

Thanks Matthias for these tips.

Samweli, do you think you can add some notes in
https://github.com/qgis/QGIS/blob/master/doc/linux.t2t (which will land in
the INSTALL file) so we won't loose these notes in the mailing list?

PS : Welcome in the Kartoza team ;-)

Le lun. 16 déc. 2019 à 22:20, Tim Sutton  a écrit :

> And thanks from me too!
>
> Regards
>
> Tim
>
> On 16 Dec 2019, at 08:47, Samweli  wrote:
>
> Hi Matthias, Thanks a lot. Compiling only the required target (eg.
> qgis_desktop) really works well!!
>
>
>
>
> --
> Sent from:
> http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-f4099106.html
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>
>
> —
>
>
>
>
>
>
>
>
> *Tim Sutton*
>
> *Co-founder:* Kartoza
> *Ex Project chair:* QGIS.org
>
> Visit http://kartoza.com to find out about open source:
>
> Desktop GIS programming services
> Geospatial web development
> GIS Training
> Consulting Services
>
> *Skype*: timlinux
> *IRC:* timlinux on #qgis at freenode.net
>
> I'd love to connect. Here's my calendar link
>  to make finding time easy.
>
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Codes in Cookbook and User manual : state of art

[DelazJ]

Hi,
Good news Alessandro. Would be nice if that makes it. Thanks.
Most of the information (other than the historic part, of course) are
already in the readme and/or in the writing guidelines as far as I
remember. Will double check when I find time.

Regards,
Harrissou

Le mer. 18 déc. 2019 à 08:48, Alessandro Pasotti  a
écrit :

> Thank you Harrissou,
>
> this is very valuable information, I think you should copy/paste it to
> some README in the docs repo (if not yet there).
>
> I'd really like to make a deep revision and update of the cookbook and put
> code snippets under automated testing, I'll ask the PSC if there are any
> funds left for such activity.
>
> Cheers
>
>
>
> On Wed, Dec 18, 2019 at 7:30 AM DelazJ  wrote:
>
>> Hi all,
>>
>> During the last meeting for docs, there were some people asking whether
>> and to which extent our documentation was linked to our API docs. While
>> some answers have been given I'd hereby like to expand a bit on the subject.
>>
>> As you probably know, we rely on Sphinx to build our docs. And we also
>> use two extensions of Sphinx to link to our code documentation (actually
>> PyQGIS):
>>
>> 1. intersphinx [0] added by Alexandre Neto: connects user manual and
>> cookbook with the pyQGIS documentation. Whenever we mention a class, it's
>> possible to enable a URL that points to the class/function doc in pyQGIS
>> website, in the corresponding release (ie for LTRs and master). Convenient
>> for users, imho.
>> Code is available at [1] and some examples at [2]. We have covered >90%
>> (not scientific, but probably true!) of what needed to be and this works
>> pretty well, as long as the pyQGIS doc builds successfully and
>> classes/functions are still in the target QGIS version.
>>
>> 2. The other extension is doctest [3] added by Arnaud Morvan at La Coruna
>> if I'm right: runs the target code snippets on QGIS and reports any error.
>> This is mainly intended to get the cookbook examples fixed faster than
>> manual trial, and less fragile. Basically, you add ".. testcode" at the
>> beginning of a snippet and ".. testoutput" with expected output at the end
>> and this code is tested at each build like if you were running it in QGIS.
>> Instructions are at [4].
>> While looking around for information to write this message, I realise
>> that Victor Olaya also made a precious initial work of updates of the codes
>> from 2 to 3 [5] automatically. But not on all the files as far as I could
>> see. Maybe could we reuse his code?
>> Today, we are far from the coverage we should have been imho, meaning
>> that there still are a lot of codes that are outdated or can become
>> outdated without noticing, because:
>> - we need people to pick each
>> - there isn't a way (or we don't know how) to test iface in the codes,
>> resulting in many interface-related codes untestable.
>>
>> Hope that clarifies, and may those who were parts of this feel free to
>> correct if I miss anything.
>>
>> Regards,
>> Harrissou
>>
>> [0] http://www.sphinx-doc.org/en/master/usage/extensions/intersphinx.html
>> [1]
>> https://github.com/qgis/QGIS-Documentation/blob/master/source/conf.py#L113
>> [2]
>> https://docs.qgis.org/testing/en/docs/user_manual/processing/console.html#creating-scripts-and-running-them-from-the-toolbox
>> [3] http://www.sphinx-doc.org/en/master/usage/extensions/doctest.html
>> [4] https://github.com/qgis/QGIS-Documentation#testing-python-snippets
>> [5]
>> https://github.com/qgis/QGIS-Documentation/pull/3406#issuecomment-458462153
>> ___
>> QGIS-Developer mailing list
>> QGIS-Developer@lists.osgeo.org
>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>
>
>
> --
> Alessandro Pasotti
> w3:   www.itopen.it
>
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] backporting bot

[DelazJ]

Hi,

I was wondering just a day before how we could have lived without this...
Thanks Denis and Gaurav.

Denis, if I want to reenable it for docs repo, I simply need to copy/paste
the action in
https://github.com/qgis/QGIS/commit/89e3f2ccf98f3563a4e3d3dbd02ed1537c93afce
to our repo and update the label or do I need anything else?

Regards,
Harrissou

Le mer. 18 déc. 2019 à 09:03, Matthias Kuhn  a écrit :

> Awesome!
>
> It will be a big timesaver. Thanks a lot!
>
> Matthias
> On 12/18/19 7:49 AM, Tim Sutton wrote:
>
> Thank you for taking care of our bot Denis!
>
> Regards
>
> Tim
>
> On 17 Dec 2019, at 19:36, Denis Rouzaud  wrote:
>
> Dear list,
>
> Thanks to the work from Gaurav Munjal who has setup another version of the
> backporting bot [0], our backporting bot is back :) [1]
>
> It's now a github action. To make it work, the API token has to in clear
> access so it can work across forks. So, I created a new user (qgis-bot)
> dedicated to this and forked qgis/qgis to qgis-bot/qgis. The PRs will be
> issued from this work.
>
> Labels should now be created as "backport [branch]".
>
> As an example, see https://github.com/qgis/QGIS/pull/33444
>
> Cheers,
> Denis
>
> [0] https://github.com/gaurav0/backport/
> [1]
> https://github.com/qgis/QGIS/commit/89e3f2ccf98f3563a4e3d3dbd02ed1537c93afce
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>
>
> —
>
>
>
>
>
>
>
>
> *Tim Sutton*
>
> *Co-founder:* Kartoza
> *Ex Project chair:* QGIS.org
>
> Visit http://kartoza.com to find out about open source:
>
> Desktop GIS programming services
> Geospatial web development
> GIS Training
> Consulting Services
>
> *Skype*: timlinux
> *IRC:* timlinux on #qgis at freenode.net
>
> I'd love to connect. Here's my calendar link
>  to make finding time easy.
>
>
> ___
> QGIS-Developer mailing listqgis-develo...@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] Fwd: [Qgis-psc] Policies document

[Paolo Cavallini]

Hi all,
if anyone knows of a policy document not listed in the ticket, please
let me know. The current situation (one developer, one documentation,
and one plugin document) looks OK to me.
Thanks for help.
Cheers.


 Messaggio Inoltrato 
Oggetto: [Qgis-psc] Policies document
Data: Mon, 16 Dec 2019 12:13:59 +0100
Mittente: Paolo Cavallini 
A: qgis-psc 

Hi all,
regarding:
https://github.com/qgis/PSC/issues/2
Condensate all policies into one page
I'd like to list all of them to our Governance menu on the website
(unless there are better proposals).
Could everybody helping me listing the current policies, adding the
links to the ticket?
Thanks.
-- 
Paolo Cavallini - www.faunalia.eu
QGIS.ORG Chair:
http://planet.qgis.org/planet/user/28/tag/qgis%20board/
___
Qgis-psc mailing list
qgis-...@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/qgis-psc
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] backporting bot

[Matthias Kuhn]

Awesome!

It will be a big timesaver. Thanks a lot!

Matthias

On 12/18/19 7:49 AM, Tim Sutton wrote:

Thank you for taking care of our bot Denis!

Regards

Tim

On 17 Dec 2019, at 19:36, Denis Rouzaud > wrote:


Dear list,

Thanks to the work from Gaurav Munjal who has setup another version 
of the backporting bot [0], our backporting bot is back :) [1]


It's now a github action. To make it work, the API token has to in 
clear access so it can work across forks. So, I created a new user 
(qgis-bot) dedicated to this and forked qgis/qgis to qgis-bot/qgis. 
The PRs will be issued from this work.


Labels should now be created as "backport [branch]".

As an example, see https://github.com/qgis/QGIS/pull/33444

Cheers,
Denis

[0] https://github.com/gaurav0/backport/
[1] 
https://github.com/qgis/QGIS/commit/89e3f2ccf98f3563a4e3d3dbd02ed1537c93afce

___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org 
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer


—








*Tim Sutton*

*Co-founder:*Kartoza
*Ex Project chair:*QGIS.org 

Visit http://kartoza.com  to find out about open 
source:


Desktop GIS programming services
Geospatial web development
GIS Training
Consulting Services

*Skype*: timlinux
*IRC:*timlinux on #qgis at freenode.net 

I'd love to connect. Here's my calendar link 
 to make finding time easy.



___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer