https://bugs.kde.org/show_bug.cgi?id=492843
--- Comment #4 from Jack <ostrof...@users.sourceforge.net> --- The feedback is to confirm whether or not the developers version does what you want. Sorry that I'm not sure if you don't understand git itself, or how the kmm team uses it. Simplified, git is a tool to manage the source code for a program. Every change made to the code is called a commit. Branches are lines or threads of commits. They are used to to track the development of different versions or feature sets. The important bit here is that the "5.1" branch contains the 5.1.3 released version, and also some further bug fixes, but no big enhancements. The "master" branch tracks development of new features, including a major rework of the ledger, including more control over seeing those reconciliation bars. You can safely test a developer version by just making a copy of your .kmy file and opening that and looking at the ledger section of the configuration dialog. Note that while there are obviously no guarantees, several folks have been using the developer version for managing our day to day finances. Because we are working hard to make the next release, which will be called 5.2, that feature will not be backported to the 5.1 branch. We can close the ticket as "FIXED" in 5.2, but we'd prefer if you can confirm it does what you want, so changes can be made now, instead of waiting for a new bug to be filed against 5.2 after it is released. -- You are receiving this mail because: You are the assignee for the bug.
