Closed Bug 729195 Opened 12 years ago Closed 12 years ago

Modify PostgreSQL database to correctly handle ESRs

Categories

(Socorro :: Database, task)

task
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: jberkus, Assigned: jberkus)

References

Details

(Whiteboard: [esr])

We need to do a number of changes to make the PostgreSQL database handle ESRs correctly:

1) add ESR to the several release channel tables

2) Modify update_product_versions() to rewrite the channel for ESR builds.

3) Change the sunset date on ESRs to match releases

4) Change update_reports_clean to handle ESRs correctly.

5) Change version_sort() to sort ESRs after Releases

6) Change update_adu to handle ESRs correctly.
   NOTE: This is waiting on Metrics pushing ESRs.

7) Verify that all matviews include ESR counts.
7)a) fix any matviews which don't.
NOTE: some matviews will not be possible to test due to the nature of the data from ESR crashes.  HangReport, for example.

8) verify that data is being displayed properly on the interface.

As of 2/21, most of the above is done in draft form.
Depends on: 729214
Whiteboard: [esr]
Database changes have been deployed on crash-stats-dev.  Adrian is current testing whether all functionality is operating as expected.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Notes for QA testing:

verify that ESR releases appear and display summaries, listings, and statistics in all interfaces in the same way other releases do.
We only backfilled to 2/22.  That crash report is on 2/20, which is why it doesn't show up consistently.
bumping to resolved per comment 4
Status: REOPENED → RESOLVED
Closed: 12 years ago12 years ago
OS: Mac OS X → All
Hardware: x86 → All
Resolution: --- → FIXED
QA verified on stage - automation is passing - manual bfts pass.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.