"John Wiegley"
writes:
> > "VL" == Vitaly Lipatov writes:
>
> VL> Can anyone enable issues on github page? Instead of separated bugzilla
> VL> hosting.
>
> I have found a friend who can get Bugzilla going. I won't enable GitHub issues
> unless
> "VL" == Vitaly Lipatov writes:
VL> Can anyone enable issues on github page? Instead of separated bugzilla
VL> hosting.
I have found a friend who can get Bugzilla going. I won't enable GitHub issues
unless we convert the Bugzilla issues first, since I don't want
On Wednesday, 13 Dec 2017 at 15:49, Michael Cooper wrote:
> 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
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
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
Please, plan a new release. It is hard to maintain application when it rare
released.
--
---
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
Can anyone enable issues on github page? Instead of separated bugzilla
hosting.
воскресенье, 22 октября 2017 г., 12:39:48 UTC+3 пользователь John Lee
написал:
>
> bugs.ledger-cli.org is not responding for me.
>
> It's linked to from this page http://ledger-cli.org/contribute.html
>
--
---