Community Packages

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#60752 - [ledger] Use branch next rather than release

Attached to Project: Community Packages
Opened by Immae (immae) - Friday, 09 November 2018, 07:09 GMT
Last edited by Doug Newgard (Scimmia) - Wednesday, 14 November 2018, 15:57 GMT
Task Type Feature Request
Category Packages
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No


The ledger project does releases very (too) infrequently, but the `next` branch is (in my opinion) stable enough to be used in production, and even has a lot of bug fixes.

The maintainer always recommends on the mailing list to use this branch when people report a bug on 3.1.1.

Would you consider using the branch rather than tagged version?

Additional info:
* package version(s) : 3.1.1
This task depends upon

Closed by  Doug Newgard (Scimmia)
Wednesday, 14 November 2018, 15:57 GMT
Reason for closing:  Won't implement
Additional comments about closing:  Without specific issues/reasons, this isn't going to happen