I would generally agree with the "if it isn't broken, don't fix it" ideal, but in Ledger's case, there is almost 2 years and 172 commits worth of development, according to Github [0], since the release of 3.1.1. There should be at least a plan for when that effort is going to be deemed suitable for a new release. Otherwise it goes to waste.
[0] https://github.com/ledger/ledger/releases On Wed, Dec 13, 2017 at 8:11 AM Eric S Fraga <e.fr...@ucl.ac.uk> wrote: > On Wednesday, 13 Dec 2017 at 04:05, Vitaly Lipatov wrote: > > Please, plan a new release. It is hard to maintain application when it > rare > > released. > > Curious: why? If an application works, why is there a need for a new > release? > > -- > Eric S Fraga via Emacs 27.0.50, org 9.1.4 > > -- > > --- > You received this message because you are subscribed to the Google Groups > "Ledger" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to ledger-cli+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- --- You received this message because you are subscribed to the Google Groups "Ledger" group. To unsubscribe from this group and stop receiving emails from it, send an email to ledger-cli+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
