Re: [QGIS-Developer] 3.10 hard freeze?

[Nyall Dawson]

On Mon, 14 Oct 2019 at 19:35, Borys Jurgiel  wrote:
>
> Dnia poniedziałek, 14 października 2019 07:32:52 CEST Denis Rouzaud pisze:
> > Hi all,
> >
> > I had a PR tagged as frozen this morning.
> > I guess this is related to the concept of hard freeze. Can someone give
> > more information on soft vs hard freeze? Any what is accepted to be merged?
>
> "Two weeks before the release a hard freeze is initiated, after which only
> fixes to severe problems and regressions introduced after the feature freeze
> are allowed in." - I found it accidentally in [1] this weekend and postponed
> my PR for 3.10.1, apparently opening a Pandora's box...

To be honest, I think most people forgot about this. I did too, until
your comment prompted my memory!

> I'm not sure if all those PRs can
> be merged into 3.10.1, or should be rather considered new features?

If they are bug fixes, then they should definitely be merged for
inclusion in 3.10.1 as soon as the 3.10 release is branched. (Just
like we'd normally do with bug fixes and point releases)

> In the
> former case I wouldn't postpone all the release schedule, but if the latter,
> that unexpected freeze should be IMHO thoroughly reconsidered.

Well, it's not unexpected. We're just all forgetful people :D

I still think the original idea has many merits, and don't think we
should discard it because of initial teething problems. The situation
as I see it:

1. we've got one set of serious known regressions, due to the snapping
threading changes. There's an open PR which may resolve these
(https://github.com/qgis/QGIS/pull/31648), which still needs
reviewing, merging and widespread user testing before final release.
Or we can play it safe for 3.10.0 and revert the earlier threading
work, pushing it back for inclusion in 3.10.1. (playing it safe would
be my vote)

2. we've a bunch of open PRs for less critical issues, which, if we
are respecting the hard freeze as intended, should definitely be
delayed until 3.10.1

3. we should be pushing out a widespread call for user testing of the
"release candidate" (i.e. the nightly snapshot which happened after
hard freeze landed)

4. we need some policy about when a bug is considered critical enough
to break the hard freeze. (I'm pretty sure everyone considers their
own personal bugs as "critical", but again, if we are respecting the
hard freeze as original designed then it's only "oh my gosh we CANNOT
possibly push out a release with THIS in it!!!11!!" level bugs which
would be applicable)

1 & 3 need to be resolved ASAP, 4 can be discussed in a nice logical
manner during lead of up final release and after ;)

Nyall


>
> Regards,
> Borys
>
> [1] 
> https://www.qgis.org/en/site/getinvolved/development/roadmap.html#feature-freeze
>
>
>
>
> ___
> 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] Error 32 (File is in Use): Trying to delete a layer file after it's been used by qgis

[Matheus Fillipe]

Hello!

I am working on a plugin that uses a temporary folder to load layer filers on 
that can end up having the same name so it is needed to have qgis closing the 
files to allow deleting them. I tested this on qgis 3.8.3 and for linux it 
worked fine but on windows still gives "error 32 , cannot remove because the 
file is in use".

process(l)
l.commitChanges()
l.endEditCommand()
QgsProject.instance().removeMapLayer(l.id())
path=l.dataProvider().dataSourceUri().split("|layername=")[0]
Path(path).unlink() #remove file returns file being used error on this line

___
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] [Qgis-psc] Is QGIS on Android?

[Marco Bernasocchi]

Hi Harrissou,

that is a very old version indeed, but not non functional, it just
supports only "old" androids, if you have a newer android the playstore
will tell you that your device is not supported (still has over 10K
downloads).
We have not updated much that version because QField is the much better
android solution for QGIS. In fact QField is QGIS core behind an highly
optimized UI and was responsible for a lot of improvements in QGIS
itself. We always make whatever possible/sensible in QGIS and reuse it
in QField then.

QField has a very large use base with over 100K downloads and and
average rating of over 4.5 (out of 1100 feedback), but I guess as you
say still not everybody is aware of it. QField also pretty much mimics
the QGIS structure where we welcome external PR, issues and fixes (so
far QField has had contributions by around 15 developers IIRC and is
translated in 13 languages more than 75%).

Obviously QField is GPL and you can use it as you see fit by simply
synchronizing or copying your data to and from your device.

So yes, I guess we should change that link, I'll discuss that tonight in
the PSC meeting.

Cheers

Marco

On 14.10.19 18:18, DelazJ wrote:
> Hi,
>
> For years now, the main page of QGIS website (https://qgis.org) claims:
>
>
>   Create, edit, visualise, analyse and publish geospatial
>   information on Windows, Mac, Linux, BSD (Android coming soon)
>
> coming soon
> And looking at the download page
> (https://qgis.org/en/site/forusers/download.html), there's an Android
> section that brings to a version of QGIS in the play store.
> Unsurprisingly, that version is old and not functional. And
> unfortunately, there are people trying to download it. Which is not
> good for the project imho.
>
> So is QGIS really on Android?
>
> Regards,
> Harrissou
>
>
> ___
> Qgis-psc mailing list
> qgis-...@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/qgis-psc
-- 
Marco Bernasocchi
OPENGIS.ch CEO
QGIS.org Co-chair
ma...@opengis.ch 
+41 (0)79 467 24 70 

OPENGIS.ch Logo 
___
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] [PyQGIS] adding a layer with an auth config ID leaks into the project

[Denis Rouzaud]

Hi Bernard,

Many thanks works perfectly.


Le lun. 14 oct. 2019 à 16:13, Bernhard Ströbl  a
écrit :

> Hi Denis,
>
> I use:
> uri = QgsDataSourceUri()
> uri.setDataSource(schemaName, tableName, geomColumn)
> uri.setConnection(thisHostName,
>  str(thisPort), thisDatabaseName,
>  "", "", QgsDataSourceUri.SslRequire, thisAuthCfgId)
> vLayerUri = uri.uri(False)
> vlayer = QgsVectorLayer(vLayerUri, displayName, "postgres",
>  layerOptions)
>
> this works as expected storing the authcfg=auth_id using QGIS 3.4
>
> Bernhard
>
> Am 14.10.2019 um 15:52 schrieb Denis Rouzaud:
> > Hi all,
> >
> > I add a layer using an authentification config ID using PyQGIS:
> >
> > uri = QgsDataSourceUri()
> > uri.setConnection(HOST, PORT, DB, None, None,
> > QgsDataSourceUri.SslPrefer, pg_auth_id)
> >
> > In the project, the credentials are written in clear text in the project
> > file:
> >
> > dbname='pub' host=geodb.rootso.org <http://geodb.rootso.org>
>
> > port=5432 user='xx' password='xx'
> >
> > Is it possible to avoid this? How?
> >
> > Cheers,
> > Denis
> >
>
>
> __ Information from ESET Mail Security, version of virus signature
> database 20178 (20191014) __
>
> The message was checked by ESET Mail Security.
> http://www.eset.com
>
>
> ___
> 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] Is QGIS on Android?

[DelazJ]

Hi,

For years now, the main page of QGIS website (https://qgis.org) claims:
Create, edit, visualise, analyse and publish geospatial information on
Windows, Mac, Linux, BSD (Android coming soon)
coming soon
And looking at the download page (
https://qgis.org/en/site/forusers/download.html), there's an Android
section that brings to a version of QGIS in the play store. Unsurprisingly,
that version is old and not functional. And unfortunately, there are people
trying to download it. Which is not good for the project imho.

So is QGIS really on Android?

Regards,
Harrissou
___
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 [246] Flow Trace approval notification.

[noreply]

Plugin Flow Trace approval by zimbogisgeek.
The plugin version "[246] Flow Trace 1.0.3" is now approved
Link: http://plugins.qgis.org/plugins/flowTrace/
___
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 [1188] MTOPOpenData approval notification.

[noreply]

Plugin MTOPOpenData approval by zimbogisgeek.
The plugin version "[1188] MTOPOpenData 1.4" is now approved
Link: http://plugins.qgis.org/plugins/MTOPOpenData/
___
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 [1516] QGIS Full Motion Video approval notification.

[noreply]

Plugin QGIS Full Motion Video approval by zimbogisgeek.
The plugin version "[1516] QGIS Full Motion Video 1.8" is now approved
Link: http://plugins.qgis.org/plugins/QGIS_FMV/
___
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 [1851] RUIAN Plugin approval notification.

[noreply]

Plugin RUIAN Plugin approval by zimbogisgeek.
The plugin version "[1851] RUIAN Plugin 1.1.0" is now approved
Link: http://plugins.qgis.org/plugins/qgis-ruian-plugin/
___
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 [752] Red Layer approval notification.

[noreply]

Plugin Red Layer approval by zimbogisgeek.
The plugin version "[752] Red Layer 2.0.2" is now approved
Link: http://plugins.qgis.org/plugins/redLayer/
___
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 [1841] VetSamp approval notification.

[noreply]

Plugin VetSamp approval by zimbogisgeek.
The plugin version "[1841] VetSamp 1.0 Experimental" is now approved
Link: http://plugins.qgis.org/plugins/VetSamp/
___
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] [PyQGIS] adding a layer with an auth config ID leaks into the project

[Bernhard Ströbl]

Hi Denis,

I use:
uri = QgsDataSourceUri()
uri.setDataSource(schemaName, tableName, geomColumn)
uri.setConnection(thisHostName,
str(thisPort), thisDatabaseName,
"", "", QgsDataSourceUri.SslRequire, thisAuthCfgId)
vLayerUri = uri.uri(False)
vlayer = QgsVectorLayer(vLayerUri, displayName, "postgres",
layerOptions)

this works as expected storing the authcfg=auth_id using QGIS 3.4

Bernhard

Am 14.10.2019 um 15:52 schrieb Denis Rouzaud:

Hi all,

I add a layer using an authentification config ID using PyQGIS:

uri = QgsDataSourceUri()
uri.setConnection(HOST, PORT, DB, None, None, 
QgsDataSourceUri.SslPrefer, pg_auth_id)


In the project, the credentials are written in clear text in the project 
file:


dbname='pub' host=geodb.rootso.org <http://geodb.rootso.org> 
port=5432 user='xx' password='xx'


Is it possible to avoid this? How?

Cheers,
Denis




__ Information from ESET Mail Security, version of virus signature 
database 20178 (20191014) __

The message was checked by ESET Mail Security.
http://www.eset.com


___
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] [PyQGIS] adding a layer with an auth config ID leaks into the project

[Denis Rouzaud]

Hi all,

I add a layer using an authentification config ID using PyQGIS:

uri = QgsDataSourceUri()
uri.setConnection(HOST, PORT, DB, None, None, QgsDataSourceUri.SslPrefer,
pg_auth_id)

In the project, the credentials are written in clear text in the project
file:

dbname='pub' host=geodb.rootso.org port=5432 user='xx'
password='xx'

Is it possible to avoid this? How?

Cheers,
Denis
___
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] 3.10.0 in hard freeze, should we branch master as unfreeze for 3.12?

[René-Luc Dhont]

Hi devs,

I remove my +1 for branching version 3.10 before release, but we have an 
issue in QGIS managing stale tag for frozen branch.


Some Pull Requests with frozen tag has been tagged stale by the github 
probot-stale.


René-Luc


___
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] 3.10.0 in hard freeze, should we branch master as unfreeze for 3.12?

[DelazJ]

Hi all,

If I may, it's maybe time to begin compilation of the changelog

Harrissou

Le lun. 14 oct. 2019 à 12:25, Mathieu Pellerin  a
écrit :

> I'm also -0 to branch off early, as I think it's a missed opportunity to
> get core devs to stick to soon-to-be-released 3.10 for as long as possible
> (and therefore oh-so slightly increase the chance of core devs stumbling on
> a bug he/she can fix prior to release :) ) .
>
> On Mon, Oct 14, 2019 at 4:02 PM Jürgen E. Fischer  wrote:
>
>> On Mon, 14. Oct 2019 at 09:14:58 +0200, Denis Rouzaud wrote:
>> > Hi all,
>> >
>> > I don't have a strong opinion, but it would be good to have pros and
>> cons
>> > to decide.
>> >
>> > Jürgen, since you are the release manager, are you saying it's not a
>> good
>> > idea (why?) or rather that you have to modify the procedure (meaning
>> more
>> > work)?
>>
>> The only gain I see is that we can just continue working on master
>> earlier.
>>
>> Branching off also means that we have to put the new version number on
>> that
>> branch prior to the actual release.   The nightly build scripts will not
>> expect
>> to see a new branch and handle it like it as if it was a new release.
>>  When to
>> merge and how to update translations in the meantime is also unclear
>> (transifex
>> is tied to the branches we current have).
>>
>>
>>
>> Jürgen
>>
>> --
>> Jürgen E. Fischer   norBIT GmbH Tel.
>> +49-4931-918175-31
>> Dipl.-Inf. (FH) Rheinstraße 13  Fax.
>> +49-4931-918175-50
>> Software Engineer   D-26506 Norden
>> https://www.norbit.de
>> QGIS release manager (PSC)  GermanyIRC: jef on
>> FreeNode
>> ___
>> 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

[QGIS-Developer] Customize QGIS interface

[bemlun]

I'm writing here to ask some questions for a thesis project. My ideas are
confused, but I'll try to be clear.

I have a GIS project that represents some historical goods in a region. Each
good has some attributes that describes the entity (like a date, a role,
etc.). My task is to create a list of queries (for example: select and
represents all goods that have a defined role in a defined time) and create
an interface, using QGIS, that allows to represent:

   1. A menu to choose the query,
   2. A form to input informations,
   3. A way to customize the presentations of results both into the map and
into a table.

I know that my question is too broad, but to be more clear I need:

   1. To know which tools allow to customize QGIS's interface (icons, fonts,
colors, all that is possible),

   2. Examples of QGIS projects where these two features are present: 1)
customized interface, 2) possibility to query.

To help I'll attach a sketch of how the interface should be. 

 



--
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

Re: [QGIS-Developer] 3.10.0 in hard freeze, should we branch master as unfreeze for 3.12?

[Mathieu Pellerin]

I'm also -0 to branch off early, as I think it's a missed opportunity to
get core devs to stick to soon-to-be-released 3.10 for as long as possible
(and therefore oh-so slightly increase the chance of core devs stumbling on
a bug he/she can fix prior to release :) ) .

On Mon, Oct 14, 2019 at 4:02 PM Jürgen E. Fischer  wrote:

> On Mon, 14. Oct 2019 at 09:14:58 +0200, Denis Rouzaud wrote:
> > Hi all,
> >
> > I don't have a strong opinion, but it would be good to have pros and cons
> > to decide.
> >
> > Jürgen, since you are the release manager, are you saying it's not a good
> > idea (why?) or rather that you have to modify the procedure (meaning more
> > work)?
>
> The only gain I see is that we can just continue working on master earlier.
>
> Branching off also means that we have to put the new version number on that
> branch prior to the actual release.   The nightly build scripts will not
> expect
> to see a new branch and handle it like it as if it was a new release.
>  When to
> merge and how to update translations in the meantime is also unclear
> (transifex
> is tied to the branches we current have).
>
>
>
> Jürgen
>
> --
> Jürgen E. Fischer   norBIT GmbH Tel. +49-4931-918175-31
> Dipl.-Inf. (FH) Rheinstraße 13  Fax. +49-4931-918175-50
> Software Engineer   D-26506 Norden
> https://www.norbit.de
> QGIS release manager (PSC)  GermanyIRC: jef on FreeNode
> ___
> 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] 3.10 hard freeze?

[Borys Jurgiel]

Dnia poniedziałek, 14 października 2019 07:32:52 CEST Denis Rouzaud pisze:
> Hi all,
> 
> I had a PR tagged as frozen this morning.
> I guess this is related to the concept of hard freeze. Can someone give
> more information on soft vs hard freeze? Any what is accepted to be merged? 

"Two weeks before the release a hard freeze is initiated, after which only 
fixes to severe problems and regressions introduced after the feature freeze 
are allowed in." - I found it accidentally in [1] this weekend and postponed 
my PR for 3.10.1, apparently opening a Pandora's box...

Now after Régis' email I see there is a number of much more important fixes 
waiting for a merge. That rule also stated "The release manager announces this 
on feature freeze", what wasn't fulfilled. I'm not sure if all those PRs can 
be merged into 3.10.1, or should be rather considered new features? In the 
former case I wouldn't postpone all the release schedule, but if the latter, 
that unexpected freeze should be IMHO thoroughly reconsidered.

Regards,
Borys

[1] 
https://www.qgis.org/en/site/getinvolved/development/roadmap.html#feature-freeze




___
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] 3.10.0 in hard freeze, should we branch master as unfreeze for 3.12?

[Jürgen E . Fischer]

On Mon, 14. Oct 2019 at 09:14:58 +0200, Denis Rouzaud wrote:
> Hi all,
> 
> I don't have a strong opinion, but it would be good to have pros and cons
> to decide.
> 
> Jürgen, since you are the release manager, are you saying it's not a good
> idea (why?) or rather that you have to modify the procedure (meaning more
> work)?

The only gain I see is that we can just continue working on master earlier.

Branching off also means that we have to put the new version number on that
branch prior to the actual release.   The nightly build scripts will not expect
to see a new branch and handle it like it as if it was a new release.   When to
merge and how to update translations in the meantime is also unclear (transifex
is tied to the branches we current have).



Jürgen

-- 
Jürgen E. Fischer   norBIT GmbH Tel. +49-4931-918175-31
Dipl.-Inf. (FH) Rheinstraße 13  Fax. +49-4931-918175-50
Software Engineer   D-26506 Nordenhttps://www.norbit.de
QGIS release manager (PSC)  GermanyIRC: jef on FreeNode


signature.asc
Description: PGP signature
norBIT Gesellschaft fuer Unternehmensberatung und Informationssysteme mbH
Rheinstrasse 13, 26506 Norden
GF: Juergen Fischer, Nils Kutscher HR: Amtsgericht Aurich HRB 100827
Datenschutzerklaerung: https://www.norbit.de/83/
___
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] pyqgis - canUninstallPlugin

[Régis Haubourg]

Hi Jacky,
just put your plugin dir on a readonly file system.
Régis

Le lun. 14 oct. 2019 à 09:25, Etienne Trimaille
 a écrit :
>
> Hi,
>
> I'm adding back the QGIS dev mailing list.
>
> Le lun. 14 oct. 2019 à 08:29, VOLPES-EXT, Jacky 
>  a écrit :
>>
>> I didn’t share any code because I don’t know how to be more clear… :/
>
>
> You said your code is not working and/or not called. So without seing it, it 
> was confusing ;-)
>
>>
>> The objective would be to prevent the plugin to be uninstalled in our 
>> specific company context :
>>
>> I want every user to have a specific set of plugins already installed in 
>> their QGis environment so they don’t have to manage installations or updates 
>> of plugins (thanks to the QGIS_PLUGINPATH environment var, where I will 
>> install and update the plugins for them).
>>
>>
>>
>> But as a result, if one user decides to uninstall a plugin, it will be 
>> uninstalled for every user.
>
>
> Seems weird to change every plugin you are going to install for them by 
> adding this flag.
> So you are using a network share for all installed plugins?
> Why not a read only directory?
>
> ___
> 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] pyqgis - canUninstallPlugin

[Etienne Trimaille]

Hi,

I'm adding back the QGIS dev mailing list.

Le lun. 14 oct. 2019 à 08:29, VOLPES-EXT, Jacky <
jacky.volpes-...@canal-de-provence.com> a écrit :

> I didn’t share any code because I don’t know how to be more clear… :/
>

You said your code is not working and/or not called. So without seing it,
it was confusing ;-)


> The objective would be to prevent the plugin to be uninstalled in our
> specific company context :
>
> I want every user to have a specific set of plugins already installed in
> their QGis environment so they don’t have to manage installations or
> updates of plugins (thanks to the QGIS_PLUGINPATH environment var, where I
> will install and update the plugins for them).
>
>
>
> But as a result, if one user decides to uninstall a plugin, it will be
> uninstalled for every user.
>

Seems weird to change every plugin you are going to install for them by
adding this flag.
So you are using a network share for all installed plugins?
Why not a read only directory?

>
___
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] 3.10.0 in hard freeze, should we branch master as unfreeze for 3.12?

[Régis Haubourg]

Hi,
Since the hard freeze tag, I realize that many dev's didn't expect
this to happen this way. The hard freeze concept doesn't seem so
clear.
We currently have some frozen PR that we need (really) to land into
the future LTR.
We did start long time ago for each of them, it is not about late
work. But we must recognize some of those were hard work (like the
parallelized snapping cache builidng thing)
We also have features for the server waiting.
And we must recognized we need more persons for the review process to
speed up the process.

I don't think we can branch now, as it is the first time we play the
hard freeze process for real for a LTR, we have to discuss some
pending PR's.

Cheers
Régis

Le lun. 14 oct. 2019 à 09:15, Denis Rouzaud  a écrit :
>
> Hi all,
>
> I don't have a strong opinion, but it would be good to have pros and cons to 
> decide.
>
> Jürgen, since you are the release manager, are you saying it's not a good 
> idea (why?) or rather that you have to modify the procedure (meaning more 
> work)?
>
> If this situation is going to happen again, it would be nice to discuss 
> before voting and take a wise decision.
>
>
> Cheers,
> Denis
>
> Le lun. 14 oct. 2019 à 09:04, Régis Haubourg  a 
> écrit :
>>
>> Hi all,
>> Same à Jürgen , -1
>> régis
>>
>> Le lun. 14 oct. 2019 à 08:36, Jürgen E. Fischer  a écrit :
>> >
>> > Hi Nyall,
>> >
>> > On Mon, 14. Oct 2019 at 09:34:13 +1000, Nyall Dawson wrote:
>> > > (Subject says it  )
>> > >
>> > > Now that we're in hard freeze for the 3.10.0 release, should we be
>> > > branching off the release-3_10 branch now and unfreezing master for 3.12?
>> >
>> > -1 as branching is part of the release process.
>> >
>> >
>> > Jürgen
>> >
>> > --
>> > Jürgen E. Fischer   norBIT GmbH Tel. +49-4931-918175-31
>> > Dipl.-Inf. (FH) Rheinstraße 13  Fax. +49-4931-918175-50
>> > Software Engineer   D-26506 Nordenhttps://www.norbit.de
>> > QGIS release manager (PSC)  GermanyIRC: jef on FreeNode
>> > ___
>> > 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] 3.10.0 in hard freeze, should we branch master as unfreeze for 3.12?

[Denis Rouzaud]

Hi all,

I don't have a strong opinion, but it would be good to have pros and cons
to decide.

Jürgen, since you are the release manager, are you saying it's not a good
idea (why?) or rather that you have to modify the procedure (meaning more
work)?

If this situation is going to happen again, it would be nice to discuss
before voting and take a wise decision.


Cheers,
Denis

Le lun. 14 oct. 2019 à 09:04, Régis Haubourg  a
écrit :

> Hi all,
> Same à Jürgen , -1
> régis
>
> Le lun. 14 oct. 2019 à 08:36, Jürgen E. Fischer  a écrit :
> >
> > Hi Nyall,
> >
> > On Mon, 14. Oct 2019 at 09:34:13 +1000, Nyall Dawson wrote:
> > > (Subject says it  )
> > >
> > > Now that we're in hard freeze for the 3.10.0 release, should we be
> > > branching off the release-3_10 branch now and unfreezing master for
> 3.12?
> >
> > -1 as branching is part of the release process.
> >
> >
> > Jürgen
> >
> > --
> > Jürgen E. Fischer   norBIT GmbH Tel.
> +49-4931-918175-31
> > Dipl.-Inf. (FH) Rheinstraße 13  Fax.
> +49-4931-918175-50
> > Software Engineer   D-26506 Norden
> https://www.norbit.de
> > QGIS release manager (PSC)  GermanyIRC: jef on
> FreeNode
> > ___
> > 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] 3.10.0 in hard freeze, should we branch master as unfreeze for 3.12?

[Régis Haubourg]

Hi all,
Same à Jürgen , -1
régis

Le lun. 14 oct. 2019 à 08:36, Jürgen E. Fischer  a écrit :
>
> Hi Nyall,
>
> On Mon, 14. Oct 2019 at 09:34:13 +1000, Nyall Dawson wrote:
> > (Subject says it  )
> >
> > Now that we're in hard freeze for the 3.10.0 release, should we be
> > branching off the release-3_10 branch now and unfreezing master for 3.12?
>
> -1 as branching is part of the release process.
>
>
> Jürgen
>
> --
> Jürgen E. Fischer   norBIT GmbH Tel. +49-4931-918175-31
> Dipl.-Inf. (FH) Rheinstraße 13  Fax. +49-4931-918175-50
> Software Engineer   D-26506 Nordenhttps://www.norbit.de
> QGIS release manager (PSC)  GermanyIRC: jef on FreeNode
> ___
> 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] 3.10.0 in hard freeze, should we branch master as unfreeze for 3.12?

[Jürgen E . Fischer]

Hi Nyall,

On Mon, 14. Oct 2019 at 09:34:13 +1000, Nyall Dawson wrote:
> (Subject says it  )
> 
> Now that we're in hard freeze for the 3.10.0 release, should we be
> branching off the release-3_10 branch now and unfreezing master for 3.12?

-1 as branching is part of the release process.


Jürgen

-- 
Jürgen E. Fischer   norBIT GmbH Tel. +49-4931-918175-31
Dipl.-Inf. (FH) Rheinstraße 13  Fax. +49-4931-918175-50
Software Engineer   D-26506 Nordenhttps://www.norbit.de
QGIS release manager (PSC)  GermanyIRC: jef on FreeNode


signature.asc
Description: PGP signature
norBIT Gesellschaft fuer Unternehmensberatung und Informationssysteme mbH
Rheinstrasse 13, 26506 Norden
GF: Juergen Fischer, Nils Kutscher HR: Amtsgericht Aurich HRB 100827
Datenschutzerklaerung: https://www.norbit.de/83/
___
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] 3.10.0 in hard freeze, should we branch master as unfreeze for 3.12?

[Peter Petrik]

+1
P

On Mon, Oct 14, 2019 at 1:49 AM René-Luc Dhont  wrote:

> +1 for branching off the release-3_10
>
> Le 14/10/2019 à 01:34, Nyall Dawson a écrit :
>
> (Subject says it  )
>
> Now that we're in hard freeze for the 3.10.0 release, should we be
> branching off the release-3_10 branch now and unfreezing master for 3.12?
>
> Nyall
>
> ___
> 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

Re: [QGIS-Developer] 3.10 hard freeze?

[Nyall Dawson]

On Mon, 14 Oct 2019 at 16:19, Peter Petrik
 wrote:
>
> Hi,
>
> I am wondering if it would be good idea to branch of the 3.10 when it is 
> already in the hard freeze mode, so we are able to merge PRs to master for 
> 3.12 release?
> That way the HF fixes would me merged directly to 3.10 branch and also the 
> tagging/release could be done on the branch before release?

Check my other email on the dev list from earlier today ;)

Nyall

>
> Peter
>
> On Mon, Oct 14, 2019 at 7:55 AM Nyall Dawson  wrote:
>>
>> On Mon, 14 Oct 2019 at 15:33, Denis Rouzaud  wrote:
>> >
>> > Hi all,
>> >
>> > I had a PR tagged as frozen this morning.
>> > I guess this is related to the concept of hard freeze. Can someone give 
>> > more information on soft vs hard freeze? Any what is accepted to be merged?
>>
>> Denis,
>>
>> My understanding is that the hard freeze is basically a "hands off"
>> for 3.10.0. We could consider 3.10.0 as being tagged for release as of
>> the freeze, and it's now just in a pending state while we put out
>> calls for testing.
>>
>> I haven't seen any fixed guidelines on what we'd allow in during this
>> time, but my 2c is that we should only let in absolutely mission
>> critical, life-threatening stuff. Everything else needs to wait till
>> 3.10.1.
>>
>> On this note, for the hard freeze period I've set the github master
>> branch to use the same branch restrictions as we apply to our LTR
>> branch (no direct pushes, PRs require all passing tests + 1
>> non-submitter review).*
>>
>> Nyall
>>
>>
>> .
>> .
>> .
>> .
>> .
>>
>> * I'm quite tempted to "forget" to set this back after hard freeze ends ;)
>>
>>
>>
>>
>> >
>> > Cheers,
>> > Denis
>> > ___
>> > 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] 3.10 hard freeze?

[Peter Petrik]

Hi,

I am wondering if it would be good idea to branch of the 3.10 when it is
already in the hard freeze mode, so we are able to merge PRs to master for
3.12 release?
That way the HF fixes would me merged directly to 3.10 branch and also the
tagging/release could be done on the branch before release?

Peter

On Mon, Oct 14, 2019 at 7:55 AM Nyall Dawson  wrote:

> On Mon, 14 Oct 2019 at 15:33, Denis Rouzaud 
> wrote:
> >
> > Hi all,
> >
> > I had a PR tagged as frozen this morning.
> > I guess this is related to the concept of hard freeze. Can someone give
> more information on soft vs hard freeze? Any what is accepted to be merged?
>
> Denis,
>
> My understanding is that the hard freeze is basically a "hands off"
> for 3.10.0. We could consider 3.10.0 as being tagged for release as of
> the freeze, and it's now just in a pending state while we put out
> calls for testing.
>
> I haven't seen any fixed guidelines on what we'd allow in during this
> time, but my 2c is that we should only let in absolutely mission
> critical, life-threatening stuff. Everything else needs to wait till
> 3.10.1.
>
> On this note, for the hard freeze period I've set the github master
> branch to use the same branch restrictions as we apply to our LTR
> branch (no direct pushes, PRs require all passing tests + 1
> non-submitter review).*
>
> Nyall
>
>
> .
> .
> .
> .
> .
>
> * I'm quite tempted to "forget" to set this back after hard freeze ends ;)
>
>
>
>
> >
> > Cheers,
> > Denis
> > ___
> > 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