Bug 390834 (related to the inability of accepting scheduled entries from the ledger) was fixed by patch 1c908e6, which will be released with 5.0.1 stable. This is a major usability issue, as not being able to work as with the previous versions forces the user to go back and forth between the ledger and the scheduled entries tab. Can this patch be included in the 5.0.0 branch?
To clarify a few things, there is no such thing as the 5.0.0 branch. 5.0.0 is a release and the number is fixed and will never change. Nevertheless, 5.0.0 marks the starting point of the 5.0 branch, which received a bunch of fixes (as the one you mention). The next maintenance release will be drawn from the tip of this branch, will be named 5.0.1 and, as you can figure out by now, will contain the fix without doubt. It's then up to the packagers to create updates for distro specific packages.
(In reply to Thomas Baumgart from comment #1) > To clarify a few things, there is no such thing as the 5.0.0 branch. > > 5.0.0 is a release and the number is fixed and will never change. > Nevertheless, 5.0.0 marks the starting point of the 5.0 branch, which > received a bunch of fixes (as the one you mention). The next maintenance > release will be drawn from the tip of this branch, will be named 5.0.1 and, > as you can figure out by now, will contain the fix without doubt. It's then > up to the packagers to create updates for distro specific packages. Then, question: should I just locally apply the patch and recompile the package (in my case, for Arch linux), or would be seen as acceptable contacting the packager to include this specific commit? Thank you for your time, by the way. I really appreciate your efforts and software.
You could ask, but I doubt Arch or any other distro would respin a package just to add a patch for a non-critical (even though very annoying) bug, especially when a bug-fix version of the application will be released shortly. Wait until 5.0.1 is released, then check how soon Arch will package it - and my guess is that they will be rather quick about it. If you really want the fix now, then recompiling yourself is probably the best short term option. As Thomas said, you don't need to apply any patch if you just compile from the head of the 5.0 branch.