Kmymoney AppImage 5.1.3

[Jack]

Pascal,

Thanks for understanding, and no apologies needed.  How to use various  
forums and mailing lists is not learned instantly, it does take time to  
figure out, and longer to turn it into your default bahavior.  I've  
been at it for MANY years.  Another thing to note is that most  
technical lists and groups strongly prefere bottom posting, so the  
entire message can be read in order, which can sometimes help with  
context, especially with threads much longer than this one.

Jack




On 2025.11.07 14:16, Pascal via KMyMoney wrote:
> Thank you Jack for your answer and my apologies for my clumsy  
> interference with an existing topic but I am not familiar with the  
> procedure.
> Regards.
> 
> Le 7 novembre 2025 19:42:35 GMT+01:00, Jack via KMyMoney  
> <kmymoney at kde.org> a écrit :
> >On 2025.11.07 06:31, pjp13 via KMyMoney wrote:
> >> Hello,
> >>
> >> In view of the difficulties reported with 5.2.1 KMM version, it  
> would be great if the KMM team would make available again a 5.1.3  
> AppImage version, until all the present difficulties are solved.
> >>
> >> Thank you very much in advance
> >>
> >> Pascal
> >>
> >Pascal,
> >
> >First, if you are starting a new topic, please create a new  
> message.  If you reply to an old message (even if you change the  
> Subject:) many mail readers will know it is a reply (noted in the  
> mail Headers:) and may get skipped by folks who no longer want to  
> read about the previous topic.
> >
> >Next, a new Appimcage from the 5.1 git branch is very unlikely to  
> happen, as Appimages are create by KDE's CI (continuous improvement)  
> pipelines, which are only enable for master branch and the current  
> stable branch, 5.2 in this case.  In addition, the team is much  
> better off spending its limited available time fixing any remaining  
> problems.
> >
> >Finally, my personal opinion is that while a few legitimate bugs and  
> regressions may have been discovered with 5.2 and 5.2.1, most are  
> matters of convenience and not show-stoppers, at least with the  
> work-arounds presented.  Yes, there are still improvements to be  
> made, but many of us are successfully using 5.2 (or even a version  
> from master branch) with great success even if the occasional hiccup.
> >
> >Jack