Greetings, all,
A few quick news items:
* Stable release 7.2 is out. This is almost purely bug fix and so will be a "stealth"
release; I'm not going to bother hackystat-announce-l with it.
* I've just committed changes to support a new "hackyCore_Build.combined.javadoc" ant
target, which produces a javadoc report that merges together the sources from all
available modules. I am wading into FileMetric evolution and figured this would be an
easy way to get global cross-referencing information. The implementation isn't 100%
elegant yet; I couldn't get all of the classpath without hardcoding references to the
jbuilder and jess jar files into javadoc.build.xml.
* The new SVN/Jira integration has the potential to provide a bunch of intriguing new
analyses. Let's make the following assumption: people commit to SVN fairly frequently,
and the Jira issue(s) provided in commit log do represent the vast majority of their work
on the stuff they are committing. If that's the case, we combine together the
DevEvent/Activity data with the Commit data with the Jira data and answer questions like
the following:
- How much time was spent on Release X?
- What proportion of time during Release X was spent on: (a) bugs, (b) new features,
(c) tasks, or (d) improvements?
- How much time was spent on (a) critical, (b) major, (c) minor, and (d)
trivial issues?
- Are these proportions changing from release to release? (telemetry!)
- What is the "velocity" (average time/issue) for each type of issue per release? Is it
changing over time?
- Do issues of a given type or priority have characteristic commit or churn?
Cheers,
Philip
