Hi Jürgen,
Am 27.02.21 um 14:16 schrieb Jürgen E. Fischer:
> Hi Ale,
>
> On Sat, 27. Feb 2021 at 09:20:06 +0100, Alessandro Pasotti wrote:
>> +1, not sure if a week is enough though, the CI blackout has been
>> hiding a few issues that must be taken care of before we ship another
>> broken releas
Hi Ale,
On Sat, 27. Feb 2021 at 09:20:06 +0100, Alessandro Pasotti wrote:
> +1, not sure if a week is enough though, the CI blackout has been
> hiding a few issues that must be taken care of before we ship another
> broken release.
Same here. The processing message about SAGA 7 should also be ch
+1 on the idea.
How far away is the OSGeo4W "reboot" from moving from testing to release? If
similar timing, would it make sense to coordinate with this 3.18.1? At the
risk of being annoyingly Windows-centric, I suspect for a lot of our Windows
userbase, the distinction between "point release of
thanks Richard,
really interesting read, and yes documentation documentation
documentation...
on this, i d like tho thanks all that help out there and, as a fantastic
trend in the last months, are helping in the QGIS OpenDays!
cheers Marco
On Sat, 27 Feb 2021, 10:15 Richard Duivenvoorde,
wrote:
Good read about 10 years looking back from Mike Bostock, BDFL of D3.js lib:
https://observablehq.com/@mbostock/10-years-of-open-source-visualization
Nice words.
Take aways:
- examples, examples, documentation (read: pyqgis and more more QGIS-tutorials
online)
- stay kind and polite to each ot
On Sat, Feb 27, 2021 at 8:15 AM Nyall Dawson wrote:
>
> So. 3.18.0 is unfortunately proving to be a bit of a dud, with numerous
> critical issues including:
>
> - georeferencer is broken: https://github.com/qgis/QGIS/issues/41770 (fixed
> now)
> - a crash in the layer properties for point cl
