madmanwoo at gmail.com
Tue Mar 8 15:44:07 PST 2016
I know it's a pain but this bug with SQL Server in 2.14 is going to hurt a
lot of people that update which use SQL Server, which is most clients of
mine. I also have a QGIS presentation next week for 100 or so people so it
would be good to be able to tell them a plan.
Mainly just looking for a plan on when we can do a 2.14.1. Work has told me
I can allocate my time as needed on QGIS so I'm happy to help fix any bugs
found for 2.14.1 if that speeds up the process.
On Mon, Mar 7, 2016 at 9:32 AM, Nyall Dawson <nyall.dawson at gmail.com> wrote:
> On 7 March 2016 at 10:28, Nathan Woodrow <madmanwoo at gmail.com> wrote:
> > Hi,
> > I know it's very early after release but I was wondering if we can do a
> > 2.14.1 release. There was a major bug in SQL Server causing labels,
> > attribute tables, features forms, etc to all play up.
> > http://hub.qgis.org/issues/14402
> > As there is a lot of SQL Server users this is a pretty major thing to not
> > have working.
> > If there is some resourcing that needs to happen for a 2.14.1 release
> let me
> > know and I will see what I can do.
> Just a note - I'd appreciate a day or so warning before a .1 release -
> I'll see what kind of workarounds I can do for the composer svg issue
> (unless someone wants to volunteer to fix this properly by
> implementing the svg cache for composer??)
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Qgis-developer