Hi Matthias,
On Wed, 31. Oct 2018 at 11:22:40 +0100, Matthias Kuhn wrote:
> I like the concept of a "release candidate".
> I think by labeling a package as RC we will encourage people to
I doubt that two letters will be a gamechanger.
> Either we call the LTR x.y.0 version a RC (instead of
Hi all,
Il 10/31/2018 12:14 PM, Jürgen E. Fischer ha scritto:
>
> Sounds like the best option - other options probably end up with the same
> result just with more effort ;)
>
>
IMHO our release procedure is OK, I agree with Juergen.
IMHO it's just a matter of communication. We should make clear
Hi Jürgen
On 10/31/18 12:14 PM, Jürgen E. Fischer wrote:
> Hi Matthias,
>
> On Wed, 31. Oct 2018 at 11:22:40 +0100, Matthias Kuhn wrote:
>> I like the concept of a "release candidate".
>
>> I think by labeling a package as RC we will encourage people to
>
> I doubt that two letters will be a
Plugin Least-Cost-Paths Network approval by pcav.
The plugin version "[1357] Least-Cost-Paths Network 0.1.2 Experimental" is now
approved
Link: http://plugins.qgis.org/plugins/LCPNetwork/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
Hello,
Now that QGIS3 is well underway I’ve been looking at getting some Python3 code
working with QGIS as standalone and plugins apps. But I have two - possibly
related persistent problems with QGIS3 and this list was suggested as a good
place to ask advice.
I’m running 3.4 (just upgraded
Hi Nyall,
> > (tools not
> > working when windows regional settings are not set to English and also
>
> Someone else will need to fix this one, it's not something I can
> reproduce. Any volunteers? If there's none, we shouldn't hold back a
> release for this.
>
On Wed, 31 Oct 2018 at 20:22, Matthias Kuhn wrote:
> But still then there will be issues and most people will only start
> testing the final release and we will run into "unknown issues" and
> "unreported issues" while working on QGIS and fix and push them without
> a big admin overhead. And we
Hi,
Compiling QGIS + server on a custom Debian machine here, install in my
local dir, make the install dir group www-data.
Put qgis_mapserv.fcgi in /usr/lib/cgi-bin
Testing an url I get ing logs:
/usr/lib/cgi-bin/qgis_mapserv.fcgi: error while loading shared
libraries:
On Wed, 31 Oct 2018 at 21:23, Jürgen E. Fischer wrote:
> So where are we with fixing the urgent bugs? EPR next friday 12:00 UTC?
>
> Next regular PR would be 2018-11-23 12:00:00 UTC
Thanks Jürgen -- for clarification do you mean 2018-11-02 or 2018-11-09?
Nyall
>
>
> Jürgen
>
> --
> Jürgen
On Wed, 31 Oct 2018 at 19:12, Giovanni Manghi wrote:
> there are also two major issues with Processing/GRASS
> not working for any multilayer datasource like gpkg),
Fixed by https://github.com/qgis/QGIS/pull/8393, which also adds unit
tests to this functionality.
> (tools not
> working when
On Wed, 31 Oct 2018 at 20:49, Richard Duivenvoorde wrote:
>
> Anyway, before releasing 3.4.1 please can other check/confirm this one:
> https://issues.qgis.org/issues/20295
Fixed in master (and only an issue on debug enabled builds). Will
backport to 3.4.
Nyall
Nothing like posting a question to trigger stumbling across the solution. It
appears that a solution was found back in the Summer in this thread:
https://www.mail-archive.com/qgis-user@lists.osgeo.org/msg40317.html
I tried adding this and both of the problems seem to have gone - although I
Hi Nyall,
On Thu, 01. Nov 2018 at 08:09:08 +1000, Nyall Dawson wrote:
> On Wed, 31 Oct 2018 at 21:23, Jürgen E. Fischer wrote:
> > So where are we with fixing the urgent bugs? EPR next friday 12:00 UTC?
> > Next regular PR would be 2018-11-23 12:00:00 UTC
> Thanks Jürgen -- for
Plugin QuickMultiAttributeEdit3 approval by pcav.
The plugin version "[1559] QuickMultiAttributeEdit3 3.0.1" is now approved
Link: http://plugins.qgis.org/plugins/QuickMultiAttributeEdit3/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
Plugin Physiocap3 approval by pcav.
The plugin version "[1399] Physiocap3 3.4.0" is now approved
Link: http://plugins.qgis.org/plugins/Physiocap3/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info:
Hi,
> Bah... feels like *every* major release someone ends up sending an email
like this...
My opinion this may show a problem with our development cycle setup. In my
previous company, different closed-sourced software, we had so called code
freeze. For example it could be 1-2 weeks before
Plugin Qgis2threejs approval by pcav.
The plugin version "[412] Qgis2threejs 2.2" is now approved
Link: http://plugins.qgis.org/plugins/Qgis2threejs/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info:
Plugin GeoDataFarm approval by pcav.
The plugin version "[1412] GeoDataFarm 2.0.2" is now approved
Link: http://plugins.qgis.org/plugins/geodatafarm/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info:
> there are also two major issues with Processing/GRASS (tools not
> working when windows regional settings are not set to English and also
> not working for any multilayer datasource like gpkg), this is for many
> a blocker for the process of adopting QGIS 3 LTR over 2.18.
both are regressions
On Wed, Oct 31, 2018 at 10:41 AM Giovanni Manghi
wrote:
> > This code freeze period will need to be associated with a strict
> definition of "blocker issues" that really need to by adressed immediatly.
> This issue here is a great example of a valid blocker.
>
> big fan of the "no known
On 10/31/18 11:08 AM, Alessandro Pasotti wrote:
>
>
> On Wed, Oct 31, 2018 at 10:41 AM Giovanni Manghi
> mailto:giovanni.man...@gmail.com>> wrote:
>
> > This code freeze period will need to be associated with a strict
> definition of "blocker issues" that really need to by adressed
>
Hi Matthias,
> > The problem here is the "known" part: if we had more testers on the
> > nightlies during the two weeks before the release date, we would
> > probably have catched some of these regression in time to fix them.
>
> Agreed, the more testing the better.
serious manual/semi-automated
On 10/31/2018 11:08 AM, Alessandro Pasotti wrote:
> We might want to introduce the concept of release candidate, in order to
> have a stricter code freeze, and give the testers and translators some
> amount of time for testing and translations, during this time only "real"
> bug fixes should be
On Wed, Oct 31, 2018 at 11:48 AM Giovanni Manghi
wrote:
> Hi Matthias,
>
> > > The problem here is the "known" part: if we had more testers on the
> > > nightlies during the two weeks before the release date, we would
> > > probably have catched some of these regression in time to fix them.
> >
Hi Giovanni,
On 10/31/18 11:47 AM, Giovanni Manghi wrote:
> Hi Matthias,
>
>>> The problem here is the "known" part: if we had more testers on the
>>> nightlies during the two weeks before the release date, we would
>>> probably have catched some of these regression in time to fix them.
>>
>>
I feel that this is a really serious issue that IMHO can justify a point
release
Peter, +1 to a release candidate
Luigi Pirelli
**
* LinkedIn: https://www.linkedin.com/in/luigipirelli
*
Hi Nyall, all,
> Soo could we break the normal cycle and get a point release out
> quickly? (Ideally with a couple of days prenotice so that anyone else
> working on urgent bug fixes could get them in too)
there are also two major issues with Processing/GRASS (tools not
working when windows
Thanks Nyall for raising this.
This indeed fells like "deja vu" and we need to advertise users that a
fresh new major release will for sure need point releases. We didn't
probably explain well enough that 3.4 is the LTR candidate, but will
definitly be a LTR in january at the end of life of 2.18
> This code freeze period will need to be associated with a strict definition
> of "blocker issues" that really need to by adressed immediatly. This issue
> here is a great example of a valid blocker.
big fan of the "no known regressions admitted", at least for LTR releases.
-- G --
Hi,
as my prototyping goes forward, I managed to create first dmg file for 3.5
master. If you want to try it out, here is the link:
https://www.dropbox.com/s/vkl9oe691lkdrqh/qgis_31102018_1.dmg?dl=0
I used Mojave 10.14, homebrew for dependecies, XCode Version 10.1 (10B61).
I would be glad for
30 matches
Mail list logo
