- Now renders (and wraps if necessary) a chart title, with additional
filter description.
- Removed more redundant code.
- Fixed divide-by-zero bug when the filter resulted in zero matches.
- Made the burndown commands read-only, so that filters apply.
- Child tasks now have their own entry date, instead of inheriting it
from the parent. This improves the ability to report new tasks in
the burndown charts, history report.
- Completed chart rendering for all three variations.
- Updated assorted documentation.
- Removed most of the obsolete code.
- Not completed:
- find rate calculation/algorithm
- fix rate calculation/algorithm
- completion date algorithm
- Infrastructure rewritten with the following benefits:
- greater performance
- reduced memory footprint
- generalized periods (daily, weekly, monthly)
- Currently graphs do not render, daily chart is still the old implementation
- Implemented burndown.daily, which is functional, but has outstanding
problems that need to be addressed:
- Slow
- Does not optimize output (i.e. contains /\S\s+$/)
- Needs generalized helper functions to reduce the size of the handler
- Fixed#555 that caused a segfault when 'log' was used with a project,
because the onProjectChange code assumes the files are still open, and
they were not. Checked all other commands for similar problem.
- Added Itay Perl to the AUTHORS file.
- Added unit test.
- Fixed bug #467, where recurring tasks were not honoring wait values.
- Fixed bug #493, which made waiting, recurring tasks invisible (thanks to
Alexander Schremmer).
- Improved feedback when announcing 'depends' attirubte changes. Now
uses task IDs instead of UUIDs, resulting in a shorter, clearer
message (thanks to Peter De Poorter).
- Fixed bug caused by using a high-resolution timer (gettimeofday) on
Windows, which only has a 10ms resolution timer. Consequently the
random number seed used was from a significantly reduced pool, which
leads to duplicate UUIDs.
- Added new 'diagnostics' command to assist with bug reporting,
testing. It answers questions such as "did you compile it yourself?",
and more.
- Specifically, it runs a UUID generation test to prove that the UUIDs
are really unique.
