Ticket for collecting issues and tasks for 4.8.2. With release 4.8.1 it turned out that not all translations were up to date or at least the releaseinfo. Not having up to date releaseinfo makes it very hard for release managers to track which translated docbook file is ready and which not. Having the same release info makes it possible after running "releasme" to run grep -rn "</release" doc/ | grep -v 4.8.x to get all not up to date files. Otherwise it is much more work to detect and report the not to date file to the translation team. Also from my experience with making releases including docs for commercial applications having different versions in the documentation files lead to questions from users similar to "Is this doc really up to date ?"
Is it possible to check the timestamp of the files to compare the translation to the original? How do the automated tools determine whether a translation is up to date, or am I wrong in thinking that proces is automated? I have not looked at what other applications do, but this issue of not all docbook files having releaseinfo the same as the released version has been the case with KMyMoney for a long time, and I don't remember anyone complaining or questioning it. In order to update those values, someone will have to carefully read each docbook file, and determine whether or not it will need any changes to reflect the behavior of the program in the current release (in this case 4.8.2). If the file does not require any changes, then it is OK to update the releaseinfo value. As I would prefer to spend the little time I have available to make the 5.0 documentation ready, I am not willing to spend the time on this task. However, if someone else determines that a docbook file does not accurately reflect 4.8.2, then I am willing to update the file as necessary. The 4.8.x series has a limited lifetime, and I think most of the developers, and even the users, would prefer to get 5.0 released as soon as possible, even if it means missing some translations for 4.8.2. Also, even if 4.8.2 is released with incomplete translations, as translations are completed after the release, they will be available in the online docs, and I am willing to make a note to that effect in the introduction section of the manual, and we could also repeat it on the main web page.
If nobody has any objections I would schedule release 4.8.2 for the beginning of February 2018. If anyone wants to work on the translation issues listed in this or this assigned ticket, this should happen as soon as possible, as experience has shown that it takes some time for the solutions to arrive in the appropriate translations
I will release 4.8.2 at the end of this week (2018 Jun 1). I just verified that translations created from 4.8 git branch contains recent gui changes (https://cgit.kde.org/kmymoney.git/commit/?h=4.8&id=7dd4bbfeb2ecbcde3bdcb2bf8e125d1abfb6fbb5), which is a major improvement compared with previous releases. :-) This release contains the following languages: Documentation (11) en_US de es et fr it nl pt pt_BR sv uk Translations (29) bs ca ca@valencia cs da de el en_GB es et eu fi fr gl hu it kk nds nl pl pt pt_BR ro ru sk sv tr uk zh_TW these fixed bugs (https://kmymoney.org/resolvedbugs.php?4.8.2) and these implemented features (https://kmymoney.org/resolvedfeatures.php?4.8.2) Windows binaries will be available at the same time. All still open bugs targeted to 4.8.2 will be moved to the next release.