Socorro:Rapid Betas:Requirements

Changes to Firefox betas

How we track beta releases will change substantially in Socorro, as follows:

• Betas will be released several times a week, in some cases daily.
• Each beta will have its own beta number in FTP and product_version_builds.
• Beta numbers will no longer be displayed as part of the version.
  • instead, all betas will be in the form "18.0b"
• Thus all betas for a specific release will be treated as the same "version".
• We will do some reporting based on the "version" (which actually also includes the channel), and some based on builds.

General changes

Topcrashers

Required reports are as follows, for a given product P:

• Topcrashers by crash date: All crashes for a particular product/version/channel, aggregated.
• Topcrashers by build date: All crashes for a particular product/version/channel/build date range

The Topcrashers by Crash Date report is equivalent to what we currently have for releases, aurora, and nightly. The Topcrashers by Build Date is new.

The TCCD should be the default view, and we should be able to switch to TCBD.

Topcrashers By Crash Date

This is our existing view of TopCrashers, which will be unchanged except for aggregating all Betas.

• User selects:
  • Product P
  • Version V (see Betas, above)
  • Time Window W, expressed as weeks back in time from now, defaulting to 1 week
• Report displays:
  • aggregated crash counts for P.V,
  • for crashes received during window W.

Topcrashers by Build Date

This will be a new "view" of the Topcrashers page. It will be largely useless for release versions, so we may not want to offer it for those. Its layout and functionality will be almost identical to the other Topcrashers view, but its data source will be a different matview.

• User selects:
  • Product P
  • Version V (see Betas, above)
  • Time Window W, expressed as weeks back in time from now, defaulting to 1 week
• Report displays:
  • aggregated crash counts for P.V,
  • for builds with build dates during W
  • for crashes received within 7 days of the Build Date

Crashes per User ("Daily crashes")

Like TCBS, the daily graph would have a switch which allows it to switch between two views, by crash date and by build date. The UI would be similar but the data source would be different.

The Crashes by Crash date is equivalent what we currently have for releases, aurora, and nightly. The Crashes by Build date (DCB) is new.

Crashes by crash date

• Crashes by crash date, for:
  • Product P
  • Version V, including the channel (e.g. 15.0beta)
  • Time Window W, expressed as weeks back in time from now, defaulting to 1 week
  • Other criteria ZZ, which are not important for these changes
• X-axis: date crash received
• Y-axis: crashes * 100 / ADU

Crashes by build date

• Crashes by build date:
  • Product P
  • Version V, including the channel (e.g. 15.0beta)
  • Time Window W, expressed as weeks back in time from now, defaulting to 1 week
  • Other criteria ZZ, which are not important for these changes
• X-axis: date of build
• Y-axis: crashes * 100 / ADU
  • for crashes within 7 days of build date

Specific changes needed - User perspective

Navigation

• Featured versions should be one per channel, e.g.: 12.0, 13.0beta, 14.0aurora, 15.0nightly. (The beta change is the only one needed immediately, the others are nice to have.)
• All reports should be shown in the drop down, e.g. Top Crashers by Crash Date, Top Crashers by Build Date, Crashes by Crash Date, Crashes by Build date
• On each of the reports with two views/versions, there should be navigation that takes you to the other view of the data.

Home page

• Default behavior is as now. There should be navigation that allows you to switch to the other view (by build date)

Backfill

There will be no backfilling. Error handling should cover cases where we try to load a report that was not generated at that time.

Questions and Issues

• Please confirm that we want to change the format of version numbers, and *how* we want to change it. Please note that:
  • any change to the format of version numbers will require significant work
  • the format change would likely need to be made retroactive, i.e. we will need to reformat old releases according to the new format.
• should we rewrite beta version numbers in the processor?
• Are we offering crash-by-build date on the home page?
• How are we handling "final betas"?
  • according to Kairo, there will be no more final betas.