https://bugs.kde.org/show_bug.cgi?id=381786

--- Comment #7 from Ralf Habacker <ralf.habac...@freenet.de> ---
(In reply to Jack from comment #6)
> Ralf,  given that there will be a 4.8.2 very soon after 4.8.1, with only
> minimal changes, would it be worth releasing 4.8.1 without all translations,
The recent 7z. tarball does not contain any translations. If we go road we
simply need to add a xz tarball with the same content. 

> and complete the translations with 4.8.2?  
The problem with with translations seem to be much older because 4.8.0 tarball
also includes outdated documentations:

./de/kmymoney/whatsnew.docbook:7:>4.7.01</releaseinfo>
./en/kmymoney/whatsnew.docbook:5:4.7.01</releaseinfo>
./es/kmymoney/whatsnew.docbook:7:>4.7.01</releaseinfo>
./et/kmymoney/whatsnew.docbook:7:>4.7.01</releaseinfo>
./fr/kmymoney/whatsnew.docbook:7:>4.6</releaseinfo>
./it/kmymoney/whatsnew.docbook:7:>4.7.01</releaseinfo>
./nl/kmymoney/whatsnew.docbook:7:>4.7.01</releaseinfo>
./pt_BR/kmymoney/whatsnew.docbook:7:>4.7.01</releaseinfo>
./pt/kmymoney/whatsnew.docbook:7:>4.5</releaseinfo>
./sv/kmymoney/whatsnew.docbook:7:>4.7.01</releaseinfo>
./uk/kmymoney/whatsnew.docbook:7:>4.7.01</releaseinfo>

To follow 4.8.0 style we can also use the available translations, which are of
the following versions

./de/kmymoney/whatsnew.docbook:7:>4.7.01</releaseinfo>
./es/kmymoney/whatsnew.docbook:7:>4.7.01</releaseinfo>
./et/kmymoney/whatsnew.docbook:7:>4.7.01</releaseinfo>
./fr/kmymoney/whatsnew.docbook:7:>4.6</releaseinfo>
./it/kmymoney/whatsnew.docbook:7:>4.8.1</releaseinfo>
./nl/kmymoney/whatsnew.docbook:7:>4.8.1</releaseinfo>
./pt_BR/kmymoney/whatsnew.docbook:7:>4.7.01</releaseinfo>
./pt/kmymoney/whatsnew.docbook:7:>4.5</releaseinfo>
./sv/kmymoney/whatsnew.docbook:7:>4.8.1</releaseinfo>
./uk/kmymoney/whatsnew.docbook:7:>4.8.1</releaseinfo>

The version list shows that 6 of 10 translations are not up to date.
There may be some progress by pinging the related translation teams.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to