Comment 1 for bug 1050853

There are two ways to approach this.

We can use the Launchpad API to check each package for each problem in the 'most common problems' API. If the version number for the most recently published version in -proposed is in the BucketVersions column family for the given problem identifier, show it in the '-proposed' filtered view of the table with the frequency value from BucketVersions.

The downside to this approach is that we do not know definitively if the crash occurred in -proposed, -updates, or the main archive since we're basing the judgement entirely on version numbers and not where each user obtained the package from. So the -proposed view might be polluted with errors that are occurring in -updates because those version numbers also existed in -proposed.

The second, though more invasive and forward-looking-only approach is to include the package origin data when creating an apport report. This could then be sent with the rest of the report to daisy, which would then maintain a separate view of the most common problems table data for each archive (ubuntu, ubuntu-proposed, ubuntu-updates, etc). We wouldn't have the pollution issue mentioned above because we'd be basing the counts entirely on the archive the errors occurred in.

Martin, Matthew, Brian, Kate, others, what do you think?