Calligra 2.7 release blockers

[Boudewijn Rempt]

On Sun, 9 Jun 2013, Cyrille Berger Skott wrote:

> On Sunday 09 Jun 2013, Boudewijn Rempt wrote:
>> On Thursday 30 May 2013 May 14:57:04 Cyrille Berger wrote:
>>> Hi,
>>>
>>> Don't forget to mark the bugs that are release blocker as such in
>>> bugs.kde.org, currently there are four release blockers:
>>>
>>> https://bugs.kde.org/show_bug.cgi?id=318724 "Opening a specific JPEG
>>> asserts Krita"
>>
>> This is because distributions are starting to move to libjpeg8, dropping
>> turbo. I've added a warning to cmake, but I'm not sure how to disable
>> building the jpeg plugin when only jpeg8 is present, nor how to fix the
>> jpeg plugin to work properly with jpeg8.
>
> Ok, I will try to come with a patch for the metadata bit, as for jpeg8, I
> guess checking if the library name contains the digit 8 with a regexp in the
> cmakelists.txt should do the trick (8 or 9 since jpeg9 is worse than
> anything).
>

That would be awesome!

>>> https://bugs.kde.org/show_bug.cgi?id=310310 "Crash when autosaving"
>>
>> I hope I have fixed this one, but I never was able to reproduce. Users of
>> krita lime do no longer report the autosave crashes, but they may still
>> happen. This was also an issue in other calligra applications, even though
>> afaik it was only reported for Words.
> Can we still close the bug ? (As NEEDMOREINFO or [MIGHTBE]RESOLVED)
>

I'm a bit torn here. It's a really bad bug that made 2.6 barely useable 
for a lot of people, weirdly enough, mainly on Ubuntu. Maybe if we disable 
autosave by default for 2.7...

I've started working for real on the kparts replacement during my 
vacation, but no ETA for that... It's not difficult, I just have to 
replace a huge chunk of code.

Boud