1312961 - extend duration to end-dates/sunset for Firefox, Fennec, and Thunderbird versions

Status: RESOLVED FIXED

(Socorro :: Webapp, task)

Description

[Wayne Mery (:wsmwk)]

Rephrased from Bug #1260420 comment 35

Thunderbird's QA testing+evaluation between build and fully unthrottled release is normally a week, and may be as long as 2-3 weeks. And once released, user uptake can be slow, plus we have less manpower than Firefox to track, monitor and verify fixes for crashes. In short, everything probably takes longer than it does for Firefox. So it would be very helpful to be able to examine topcrash, crashes-per-day, etc for a longer time for each version. We especially need more overlap for
* transitioning from esr-N to esr-N+1 (we sometimes never fully unthrottle esr-N.0)
* betas

Considering those thoughts and what I see at https://crash-stats.mozilla.com/admin/featured-versions/#Thunderbird I propose:
* 6 months for releases (current featured list is inconsistent, varies 4-5 months)
* 5 months for betas (current featured list is inconsistent, varies 2-3 months,
   we average about builds 2 per beta)
* 3 months for nightly and aurora(currently looks to be 2 months)

Does this sound reasonable?

Comment 1

[Peter Bengtsson [:peterbe]]

Those intervals (buildID --> sunset date) comes from this piece of code:
https://github.com/mozilla/socorro/blob/master/socorro/external/postgresql/raw_sql/procs/sunset_date.sql#L21
(It's so old that the only git history we have is from 2012 when one big fat schema.sql file was broken up into smaller .sql files)

As you can see, the code in there is pretty plain but it does NOT distinguish between products. 

I recommended, if possible, that we morph this bug to not be about Thunderbird if the Firefox RelEng people can agree. 

As far as I know this sunset date is only applicable to the drop-downs on the home page and on Crashes per Day. 
I very much doubt that it's used in processors because I recently saw a processed crash for Firefox 3.6.

Comment 2

[Wayne Mery (:wsmwk)]

> I recommended, if possible, that we morph this bug to not be about Thunderbird if the Firefox RelEng people can agree. 

I remember doing exactly that long ago :)
Hopefully our needs align

Comment 3

[Liz Henry (:lizzard) (relman/hg->git project)]

I like the idea of just doubling the time intervals we have now. That should cover pretty far back. The only down side is having a long dropdown menu. That doesn't bother me!

Comment 5

[Liz Henry (:lizzard) (relman/hg->git project)]

I will be wanting to have easy access to the stats for 47.0 and 47.0.1 around the middle of next week, is it possible you could deploy this early next week?

Comment 6

[Peter Bengtsson [:peterbe]]

Attachment: Link to Github pull-request: https://github.com/mozilla/socorro/pull/3565

This PR doesn't close the bug automatically because once landed, we need to upgrade the admin nodes and apply the migration.

Comment 7

[[github robot]]

Commit pushed to master at https://github.com/mozilla/socorro

https://github.com/mozilla/socorro/commit/90ab6b0c2f9ed04968701e11f46c1bc082559002
bug 1312961 - increase default sunset date (#3565)

* bug 1312961 - increase default sunset date

* leave out downgrade

* pass in downgrade

Comment 8

[Peter Bengtsson [:peterbe]]

Next up, I need to apply alembic migrations on stage and prod.

Comment 9

[Peter Bengtsson [:peterbe]]

This stored procedure has now been updated on stage and prod. Yay!

Comment 10

[[github robot]]

Commit pushed to master at https://github.com/mozilla/socorro

https://github.com/mozilla/socorro/commit/ad20ce471e9a4bf4559303069169c8a77bee5d20
bug 1312961 - correct comment about sunset date (#3708)