Hi,
Was this bug fixed on 2.18.5-2 ? Would it be present on 2.14.13-2 as well?
If this is a major bug maybe 2.18.4 should be the default on the download
page till it fixed ?
On 1 April 2017 at 05:27, Nyall Dawson wrote:
> Hi Jürgen, all
>
> I'm wondering if there's any chance of an immediate fo
Just want to say to both Juergen and Nyall that the amount of work you put
into QGIS is unbelievable. I'm sorry this means you have more work to do,
but for the rest of us, we get to have an even bigger version number. And
that's *better*.
Tom
-
Buy Pie Spy: Adventures in British pastry 201
Where's the fun in software if we aren't breaking stuff last minute ;)
On Sat, 1 Apr 2017, 7:38 PM Jürgen E. Fischer wrote:
> Hi Nyall,
>
> On Sat, 01. Apr 2017 at 12:27:37 +1000, Nyall Dawson wrote:
> > I'm wondering if there's any chance of an immediate follow up to the
> > 2.18.5 release with
Hi Nyall,
On Sat, 01. Apr 2017 at 12:27:37 +1000, Nyall Dawson wrote:
> I'm wondering if there's any chance of an immediate follow up to the
> 2.18.5 release with a quick bug fix release.
Oh no. Took me until wednesday to cleanup the mess - and now there's even
more.
> Totally my fault
Get in
Hum Nyall,
double checking here.. (since I have a huge work load for a training course
on monday with freshly installed 2.18.5).
Is there any chance this is an easter egg?
If so, please tell us soon
Régis
2017-04-01 4:27 GMT+02:00 Nyall Dawson :
> Hi Jürgen, all
>
> I'm wondering if there's any
Hi Jürgen, all
I'm wondering if there's any chance of an immediate follow up to the
2.18.5 release with a quick bug fix release.
Totally my fault, but when I backported
https://github.com/qgis/QGIS/commit/90f381 I missed some changes which
had occurred between master and 2.18, with the result tha
