Merge-tracking metrics for HWE projects

= Merge Report Meeting 2011-05-12 =
== Overview ==
* The merge report is a report aimed as a visual aid targeting enablement bugs and the N+1 gap.
  * This data is driven by the tags, and hwe-* projects used during enablement
  * see PlatformServices/HardwareEnablement/Process/BugWorkflow|BugTags
* This report will continue to evolve, and this session is to provide a review of where we're at, and to gather requirements for where we're going.

* jk demo'd local copy of the report
  * https://chinstrap.canonical.com/~jk/merge-report/ is available an an example, although bug data is not up to date.

== Requirements / Moving Forward ==
* Can we track upstream fixes in the public bug?
  * Without adding more overhead?
  * Potentially add upstream bug tasks to each bug and track upstream tasks within report. (action)

* jk sorting out a timeline of release(s) rather than per bug report.
  * This will help all of us identify trends in bugs.

* A process is needed as a way to sort out bugs fixed by a -stable update, or a BIOS fix. (action)

* Two classes of bugs
  * non-critical / blocker bugs
  * bugs that stop you from upgrading
  * How can we identify bugs easily that fit into these two categories (action)

* Proactive notifications of release blocking bugs via email as Ubuntu freeze dates approach (action)

* Public-only bugs:
 * indicated by a specific tag (currently blocks-hwcert-enablement)
 * plus a nomination for the appropriate N+1 series

== Update 2011-10-13 ==
 * Migrated remaining two workitems to hwe-p-misc

Work items:
[vanhoof] Formalise how we track upstream fixes via public bugs: DONE
[vanhoof] Add nomination ack/nack to HWE Bug Process wiki (PM/EM/Engineer workflow): DONE
[vanhoof] automate nomination report: INPROGRESS
[vanhoof] get jk/vanhoof permissions to accept nominations on hwe bugs: DONE
[anthonywong] Document merge report on HWE wiki: DONE
[jk-ozlabs] begin work on a top-down per release view (in addition to a per bug report): DONE
[vanhoof] Sort out a way to define a 'fix' where no public bug exists (-stable updates, BIOS, etc): INPROGRESS
[jk-ozlabs] Sort out a public project and/or a better way of tracking public bugs (without a corresponding private bug) for the Merge Report (Within the confines of lp.net/canonical-hwe-projects): DONE
[lexical] Send jk examples of public bugs with no associated private bug (Asus jack sense feature comes to mind): DONE
[jk-ozlabs] Enable parser to find series fixed in Launchpad bug update (as fallback method of obtaining data): DONE
[vanhoof] Find a way to 'tag' bugs which are release critical, and would cause an upgrade failure: DONE
[jk-ozlabs] generate automated email to HWE team as critical deadlines (freeze)/bugs approach: INPROGRESS
[vanhoof] get report hosted on hwe.canonical.com, and generating automatically: DONE