[Qgis-developer] No fix for 2.0 for #8068, wrong font display in qgis server

[Tim Sutton]

Hi


On Tue, Sep 3, 2013 at 10:35 AM, rldhont <rldhont at gmail.com> wrote:

>  Hi Tim,
>
>
> What about the 6 others blockers ?
>
> 2 seem close to resolution : #8487 and #7441
>

Unfortunately anything past the cut off date is going to have to stay in a
'known issues' list to be addressed in the next release.

I have postponed the branching of the release yet another day for  Nathan
and Salvatore to fix another last minute crash they found on IRC so if
anyone has the ability to resolve these over the course of tomorrow, now is
your chance!

Regards

Tim


>
> Regards,
> René-Luc D'Hont
> 3Liz
>
> Le 03/09/2013 10:20, Tim Sutton a écrit :
>
> Hi
>
>
> On Tue, Sep 3, 2013 at 5:40 AM, Larry Shaffer <larrys at dakotacarto.com>wrote:
>
>>     Hi,
>>
>>  After many hours of visual testing, monkeying with the code and
>> generally banging my head against a wall, I've come to the conclusion I can
>> not commit the partial fix I have for this issue [0] without possibly
>> causing issues in other types of output: canvas, composer, PDF, etc. Part
>> of this is due to the way I coded the new label components and now it looks
>> like there is definitely something screwy with the way server handles
>> fonts. There are too many variables and no really useful unit test suite
>> yet.
>>
>>  I suggest the following course of action:
>>
>>  1) Release the desktop version with this as a known blocker, albeit
>> mostly related to server output.
>>
>>  2) Have an experienced dev review the label painting code who is
>> familiar with both labeling and server, e.g. Marco H., etc.
>>
>>  3) While the code is being reviewed, I can work towards finishing the
>> initial unit test suite for labeling (with crosschecks between canvas and
>> composer, server outputs). Absolutely no labeling features are added or bug
>> fixes committed until there is a functioning test suite for the most common
>> labeling uses and outputs.
>>
>>  4) When this issue is appropriately fixed and tested, look at possibly
>> releasing an updated server component/pkg, if needed.
>>
>> [0] http://hub.qgis.org/issues/8068
>>
>>
>  Thanks Larry. If there are no other objects I will go ahead with
> branching for release tonight.
>
>  Regards
>
>  Tim
>
>
>>  Regards,
>>
>> Larry Shaffer
>> Dakota Cartography
>> Black Hills, South Dakota
>>
>> _______________________________________________
>> Qgis-developer mailing list
>> Qgis-developer at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/qgis-developer
>>
>
>
>
>  --
> Tim Sutton - QGIS Project Steering Committee Member (Release  Manager)
> ==============================================
> Please do not email me off-list with technical
> support questions. Using the lists will gain
> more exposure for your issues and the knowledge
> surrounding your issue will be shared with all.
>
> Irc: timlinux on #qgis at freenode.net
> ==============================================
>
>
> _______________________________________________
> Qgis-developer mailing listQgis-developer at lists.osgeo.orghttp://lists.osgeo.org/mailman/listinfo/qgis-developer
>
>
>


-- 
Tim Sutton - QGIS Project Steering Committee Member (Release  Manager)
==============================================
Please do not email me off-list with technical
support questions. Using the lists will gain
more exposure for your issues and the knowledge
surrounding your issue will be shared with all.

Irc: timlinux on #qgis at freenode.net
==============================================
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-developer/attachments/20130904/e0892608/attachment.html>