Error Linking konlinetasks_sepa

Ralf Habacker ralf.habacker at freenet.de
Fri Nov 24 22:09:17 UTC 2017


Am 21.11.2017 um 01:00 schrieb Jack:
> On 2017.11.20 18:13, Ralf Habacker wrote:
>> Am 20.11.2017 um 23:19 schrieb gary at duzan.org:
>> >    No, I haven't spent time on this recently, and yes, it had been
>> through
>> > multiple reconfigure/rebuild cycles. I had been hoping to try an
>> > official 4.8.1 source tar at some point, but that seems to keep being
>> > pushed back.
>> You would be happy with the recent translation state (see
>> https://bugsfiles.kde.org/attachment.cgi?id=108858 from a 2017-11-14) ?
>>
>> The current process requires to compare the releaseinfo tag from each
>> docbook file in each translation to the related file of the base
>> translation to get an idea how far the translation state is. You cannot
>> look for docbook files not having a releaseinfo with the recent app
>> version e.g. grep -rn "<releaseinfo>" | grep -v 4.8.1
>>
>> See for example
>> https://docs.kde.org/stable4/de/extragear-office/kmymoney/ which
>> indicates that the documentation is for 4.6 while this page
>> https://docs.kde.org/stable4/de/extragear-office/kmymoney/whatsnew.htm
>> is for 4.8.1 and this page
>> https://docs.kde.org/stable4/de/extragear-office/kmymoney/makingmostof.html
>>
>> refers to 4.5.
>>
>> If you find a way to speed up this process, you are very welcome.
>> > If that isn't going to be happening soon, I have some
>> > vacation coming up next week, and I can try setting up a separate
>> > git-based package then.
>> It is a simple task to create a source tar ball by running the
>> "releaseme" script, but because 4.8.0 has been released more than a year
>> before
>> (https://sourceforge.net/projects/kmymoney2/files/KMyMoney-Windows/4.8.0/)
>>
>> and noone cares about releasing 4.8.1 for a whole year, waiting a few
>> weeks more doesn't matter I think.
>> From my previous experience with KDE projects (umbrello) I learned a
>> rule that documentation are freezed shortly before releasing version
>> x.x.0 (or x.x-1.80) so my current assumption is that the recent
>> documentation  should be "mostly" up to date - the "whats new" page has
>> been updated recently by Jack.
>> Ralf
> Given that we plan to do a 4.8.2 release (with minimal changes from
> 4.8.1,) I have already said I am happy to release 4.8.1 with
> incomplete translations.  In fact, if docbooks not changed by me to
> 4.8.1 are not fully translated, then it is likely the previous release
> had the same problem.  
The difference to 4.8.0 is that the 'what new' page has been updated and
is currently only been translated for 6 of 11 included languages (54 %).
The 'what's new' page is probably one of the most frequented pages :-(
The releaseme script uses a 75% completeness rate to decide which
language is included and which not. If we use that limit too, we are
below this limit.
> When we are ready for 4.8.2, we can do a proper doc freeze and repeat
> the request to the translation teams.
There are enough open bugs to thinking about a 4.8.2 release. I filed a
related ticket, see https://bugs.kde.org/show_bug.cgi?id=387280. I
learned from recent experiences with translations (Estonian translation
will be done latest in Januar, see
https://marc.info/?l=kde-i18n-doc&m=151050920321516&w=2) that it is
required to start now with 4.8.2 work for translation docbook up to date
check and fixing to have it complete in Februar 2018.

Some additional notes:
1. the 4.8.1 release would be 4.8.1-1 because the source tar ball needs
to be named different as the one already uploaded
2. beside the translation there is  - from my point of view - a much
more important issue in the code base: I'm refering to Bug 385857
(https://bugs.kde.org/show_bug.cgi?id=385857), which makes reports using
"Convert to base currency" unreliable in case the report interval is not
daily. The related bug fix seems to be incomplete (reported with bug
387040, https://bugs.kde.org/show_bug.cgi?id=387040). Fixing this bug 
by me will probably require some weeks from now on, because I need to
dig into the report implementation very deeply. This will delay an
official 4.8.1-1 release probably to the second week of December or
later. Fortunally this will give translators additional time to complete
translations.

If anyone is there who has time to fix or at least can give some
information how to fix to speed up the release, be welcome.

Ralf


More information about the KMyMoney-devel mailing list