842865 - Tracking bug for 25-jun-2013 migration work

Status: RESOLVED FIXED

(Release Engineering :: General, defect)

Description

[John O'Duinn [:joduinn] (please use "needinfo?" flag)]

Instructions: https://wiki.mozilla.org/ReleaseEngineering:MergeDuty

Comment 1

[[e-mail] (:bhearsum)]

Migration work is complete.

Comment 2

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

We missed updating bouncer for the version bumps, not surprising given it falls into a documentation black hole. I've updated firefox-nightly-latest, firefox-aurora-latest, firefox-aurora-stub.

Not sure what to do about this going forward. We need to do bump locations until bouncer picks up these changes from some other data source (bug 801208, bug 813652). The nightly product can be done after the first nightly with the new version. The two aurora ones need to wait for QA signoff and re-enabling aurora updates, so should probably be part of that bug.

Comment 3

[[e-mail] (:bhearsum)]

(In reply to Nick Thomas [:nthomas] from comment #2)
> We missed updating bouncer for the version bumps, not surprising given it
> falls into a documentation black hole. I've updated firefox-nightly-latest,
> firefox-aurora-latest, firefox-aurora-stub.
> 
> Not sure what to do about this going forward. We need to do bump locations
> until bouncer picks up these changes from some other data source (bug
> 801208, bug 813652). The nightly product can be done after the first nightly
> with the new version. The two aurora ones need to wait for QA signoff and
> re-enabling aurora updates, so should probably be part of that bug.

Ugh, sorry about that. It's even documented already on https://wiki.mozilla.org/ReleaseEngineering:MergeDuty.

We talked at one point about having the nagios checks around these installers verify version numbers...I don't know what became of that. Not sure how that would work for Aurora, either.