I promised to share this utility recently. If I had my druthers, I'd
hold off until it was "finished" and "ready for public use". But we all
know how that goes. So, I've cloned and published the repository I keep
for documenting my understanding of the ticket system that happens to
contain my report generator utility.
The utility reads a template file and writes a report document that
contains sections for each specified ticket report in a fossil
repository. The intent is to be able to easily generate a report to
include with a project release showing what tickets were addressed by
this release, possibly including the full text of related tickets.
https://chiselapp.com/user/rberteig/repository/Ticketer/home
I would classify this as "pre-alpha" and "works for me today". Your
mileage will vary. I'd be happy to have collaborators or even just bug
reports.
To get started, clone that repository, and look in the reporter folder
for readme.pdf and sample.report.
Major known TODO items include writing some actual end-user
documentation, packaging it up with an installer for distribution, and
putting some more thought into dealing with custom ticket schema in general.
It is written in Lua, assumes that fossil is configured to include json
support, and that Markdown is a suitable intermediate language in which
to write its reports. By default, it invokes Pandoc which invokes
LuaLaTeX to translate the markdown output to PDF.
--
Ross Berteig [email protected]
Cheshire Engineering Corp. http://www.CheshireEng.com/
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
