667672 - Clean up products with Check Now set in bouncer

Status: RESOLVED FIXED

(Release Engineering :: General, defect, P2)

Description

[Nick Thomas [:nthomas] (UTC+12)]

Products with Check Now set are checked on the mirrors every 5 minutes, which doesn't make sense for old releases. And we have a lot of old releases with it still set.

Comment 1

[Nick Thomas [:nthomas] (UTC+12)]

Trimmed from 105 products to 68, by unsetting Check Now for:
Firefox-4.0b11
Firefox-4.0b11-Complete
Firefox-4.0b11-Partial-4.0b10
Firefox-4.0b12
Firefox-4.0b12-Complete
Firefox-4.0b12-Partial-4.0b11
Firefox-4.0rc2
Firefox-4.0rc2-Complete
Firefox-4.0rc2-Partial-4.0rc1
Firefox-5.0b2
Firefox-5.0b2-Complete
Firefox-5.0b2-Partial-5.0b1
Firefox-5.0b3
Firefox-5.0b3-Complete
Firefox-5.0b3-Partial-5.0b2
Firefox-5.0b4
Firefox-5.0b4-Complete
Firefox-5.0b4-Partial-5.0b3
Firefox-5.0b5
Firefox-5.0b5-Complete
Firefox-5.0b5-Partial-5.0b4
Firefox-5.0b6
Firefox-5.0b6-Complete
Firefox-5.0b6-Partial-5.0b5
Firefox-5.0b7
Firefox-5.0b7-Complete
Firefox-5.0b7-Partial-5.0b6
Firefox-Mobile-1.1
Firefox-Mobile-1.1-N900
Firefox-Mobile-4.0
Firefox-Mobile-4.0.1
Firefox-Mobile-4.0b5
Firefox-Mobile-4.0rc1
Firefox-Mobile-5.0b2
Firefox-Mobile-5.0b3
Firefox-Mobile-5.0b4

There are some older SeaMonkey and Thunderbird releases that could get the chop, but are still on the mirrors. We'll handle that separately.

Generally I try to follow this sort of procedure
* MyApp 1.1.4 is released
* Leave 1.1.3 on the mirrors for a few more days, then add it to the rsync exclusion file
* After a few days unset Check Now in bouncer

The point of the first delay is to give users a chance to finish their 1.1.3 update download, or switch to mindlessly looping on 1.1.4 instead. The second one gives the mirrors a chance to do the deletion while we're still checking them regularly. If we were to unset Check Now immediately we'd only be checking once a day, so could be sending 302's to 404s for up to 24 hours.