CodeTools proposal: "friday stats"

[Stuart Marks]

Hi Jon,

Great to see this moving forward!

Speaking from the warnings cleanup experience, at one point I had posted an awk 
script to analyze build warnings, and at the time the best way to share it was 
... on a wiki page. I heard that the LJC guys had made some changes, but I 
don't think I ever saw those changes, and they certainly weren't checked in 
anywhere. Not that this was a big deal. But it does show that even apparently 
simple things like that really ought to be in a repository where they can be 
shared and versioned consistently.

Anyway I'm all for it.

s'marks




On 6/17/13 5:34 PM, Jonathan Gibbons wrote:
> Subject: 	CodeTools proposal: "friday stats"
> Date: 	Mon, 17 Jun 2013 11:35:00 -0700
> From: 	Jonathan Gibbons <jonathan.gibbons at oracle.com>
> To: 	code-tools-dev at openjdk.java.net
>
>
>
> Name: Friday Stats
>
> Summary: A collection of small custom utilities for analyzing the JDK
> code base.
>
> Proposed by: Jonathan Gibbons
>
> Rationale:
>
> For a while now, some developers on the JDK team have indulged in an
> occasional practice of generating and publishing "Friday stats". These
> are emails, typically on a Friday, containing interesting or useful
> statistics about the OpenJDK code base. The emails are intended to
> highlight issues needing attention and to highlight progress that has
> been made.
>
> Often, these emails are the result of creating and running small utility
> programs to analyze the code base and related files, like build logs. It
> is proposed that we should publish any such utilities to a new repo
> under the CodeTools umbrella. The goal is to make these utilities more
> widely available to anyone helping in "code cleanup" or reducing
> "technical debt" and to explore the usage of these utilities to provide
> "continuous monitoring" in a CI environment.
>
> A popular topic for these emails has been the number of warnings
> generated when building OpenJDK, which continues to be an issue, even
> though significant progress has been made on a number of fronts. There
> are three utilities that we would like publish in this area.
>
> 1. A tool to report on the number of lint and doclint messages found in
> a given set of packages in a project.
>
> 2. A tool to analyze a build log and categorize the many various
> messages that a generated.
>
> 3. A simple tool to remove the expected set of "informational" messages
> from a build log, leaving the set of messages that deserve attention.
> The number of such lines is also generated, to facilitate generating a
> trend graph to monitor progress over time.
>
> More details on these tools will be provided in due course. Although
> these initial utilities are focussed on warnings and other diagnostics
> occurring during an OpenJDK build, the name "Friday stats" is intended
> to be broad enough to include any utilities to generate any statistics
> about OpenJDK that might be of interest to OpenJDK developers while
> working on the OpenJDK code base.code-
>
>
>