I've just taken a look at the FindBugs report from last nights build, which now shows for each module the number of FindBugs warnings for which we eventually want to fail the build. Before we take that dramatic step, we need to eliminate all existing fail-level warnings from the system. What I've done is create a list in alphabetical order of all of the modules with any fail-level warnings, and then partitioned the list into five somewhat equal amounts along somewhat logical boundaries, then assigned them to developers as follows:
24 hackyApp_CGQM 5 hackyApp_Course 1 hackyApp_Experiment 15 hackyApp_Mds 1 hackyApp_Pri ---------------- 46 Mike 13 hackyApp_PrjSize 17 hackyApp_Review 9 hackyApp_StdCmd 2 hackyApp_TelemetryControlCenter 10 hackyApp_Workflow -------------------- 51 Hongbing 15 hackyCore_Common 15 hackyCore_Installer 27 hackyCore_Kernel 3 hackyCore_Report 11 hackyCore_Telemetry --------------------- 71 Philip 2 hackyStd_Activity 13 hackyStd_Build 1 hackyStd_CodeIssue 4 hackyStd_Dependency 1 hackyStd_FileMetric 6 hackyStd_Issue 3 hackyStd_ReviewActivity ----------------------- 30 Julie 1 hackySensor_Ant 2 hackySensor_CLI 2 hackySensor_CPPUnit 11 hackySensor_CVS 1 hackySensor_Eclipse 2 hackySensor_Emacs 2 hackySensor_Jupiter 1 hackySensor_OpenOffice 1 hackySensor_Vim 1 hackySensor_XmlData -------------------- 24 Austen Since Cedric put in so many hours already on this task, I think it is only fair that he be a spectator to this event. I will next create five Jira issues, one for each of these module sets. To make this more fun, prizes will be awarded for the fastest closure of these particular issues! Cheers, Philip p.s. Cedric--could you email out instructions on how to locally run FindBugs to check just the fail-level FindBugs tasks so people can test their fixes?
