List view

• Relating Source Code Features and Bug Reports

  We need Groundhog to be capable of relating source code elements, issues, and VCS activity. For this particular milestone, we'd like to know if classes and package that include concurrent programming constructs are usually associated with issues. One of our goals is to discover whether concurrent programming constructs are good predictors for bugs.

  Overdue by 12 year(s)

  •

  Due by August 5, 2013

  •0/3 issues closed
  0% complete3 open0 closed

• More on Fork Activity and Initial Source Code Analysis

  This milestone involves obtaining more complex information about fork activity. See the associated issue for more information. BTW, that issue should probably be broken down into smaller issues. An issue originally associated with the first milestone was moved to this one. It requires both (i) source code analysis; and (ii) analysis of metainformation to determine what it means for a project to be mature (because that can be determined in terms of a number of factors).

  Overdue by 13 year(s)

  •

  Due by July 1, 2013

  •1/3 issues closed
  33% complete2 open1 closed