TaskJuggler III 0.0.7 has been released
Chris Schlaeger
There have been TaskJuggler III releases about every 2 months this
year. So, it's about time for the next release to stick with that
cadence.
I'm happy to announce the release of TaskJuggler III 0.0.7!
TaskJuggler III is a rewrite of TaskJuggler 2.x that aims to move
TaskJuggler into the age of web applications while not losing it's
roots on the command line. This release features the usual large round
of bug fixes and feature enhancements. A big thanks to everybody who
submitted bug reports and helped to improve TaskJuggler!
The built-in web server can now serve HTML reports that have some of
their attributes defined by the referencing report. See the reportlink
block generator section in the manual (
http://www.taskjuggler.org/tj3/manual/Rich_Text_Attributes.html#Block_and_Inline_Generators).
To use the web server, start the TaskJuggler daemon (tj3d) with the -w
option. See 'tj3d --help' and the manual for more details. The full
change log can be found at
http://www.taskjuggler.org/tj3/doc/files/CHANGELOG.html.
Now that Ruby 1.9.2 has been officially released, this is the
preferred and recommended runtime environment. For users that only use
the tj3 tool, Ruby 1.8.7 will still work. To use the web server or the
timesheet infra structure, Ruby 1.9.2 is required. I had hoped to get
a bug-fixed version of ruby-mail for this release. Unfortunately, the
maintainer did not stick to his commitment to release a new version
with the submitted patches. So, we're stuck with the a lot less broken
ruby mail 2.1.3 release.
To install TaskJuggler 0.0.7, please follow the instructions in the
manual: http://www.taskjuggler.org/tj3/manual/Installation.html#Installation
For problems or questions, please go to the user forum:
http://groups.google.com/group/taskjuggler-users. This is the place
where users help other users.
Bugs should be reported here: http://groups.google.com/group/taskjuggler-bugs
When posting to the TJ mailing list, please send regular emails to the
corresponding list email addresses listed on the page. Try to avoid
using the Google Groups web front-end as it does not support
attachments. Example projects should always be attached and not pasted
into the email to prevent them from getting corrupted by line breaks.
Chris