Closed Bug 910442 Opened 12 years ago Closed 12 years ago

Stub Installer on aurora.mozilla.org is serving Firefox 24.0a2 20130805

Categories

(Release Engineering :: Release Requests, defect)

Product:
Release Engineering
Component:
Release Requests
Platform:
x86
Windows 8
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: u279076, Assigned: nthomas)

Details

It appears that the Aurora stub installer is currently serving Firefox 24.0a2 20130805. 1. Load http://aurora.mozilla.org 2. Click the green download button > Downloads https://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla-aurora/firefox-25.0a2.en-US.win32.installer-stub.exe 3. Load the Stub Installer and let it install Firefox 4. Start Firefox and go to about:support > User Agent: Mozilla/5.0 (Windows NT 6.2; rv:24.0) Gecko/20130805 Firefox/24.0
Looks like the configuration in download.m.o wasn't updated after QA signed on on Aurora updates.
Assignee: nobody → nthomas
Component: Installer → Releases
Product: Firefox → Release Engineering
QA Contact: bhearsum
Version: 25 Branch → unspecified
Fixed. We need to figure out some better process here, as this has happened before.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
(In reply to Nick Thomas [:nthomas] from comment #2) > Fixed. Verified fixed. Thanks for the quick turnaround. > We need to figure out some better process here, as this has happened before. Verifying the Stub Installer was not previously part of QA's Aurora sign-off. I am integrating a manual spotcheck to our checklist and will work with the Automation Development team to see if we can get this manual spotcheck automated. I consider this gap filled on QA's end going forward. If there is anything RelEng or WebDev can do to fill this gap so that this QA work is unnecessary, great.
Status: RESOLVED → VERIFIED
I updated our doc at https://wiki.mozilla.org/ReleaseEngineering:MergeDuty, to say that bouncer should be changed when we get the request to re-enable updates on Aurora. Does that match up with where you're adding your spotcheck ?
(In reply to Nick Thomas [:nthomas] from comment #4) > I updated our doc at https://wiki.mozilla.org/ReleaseEngineering:MergeDuty, > to say that bouncer should be changed when we get the request to re-enable > updates on Aurora. Does that match up with where you're adding your > spotcheck ? I think so. I added the spotcheck as a checklist item *after* we've verified Aurora updates are unthrottled. Does that match up with you?
Sounds good to me, thanks.
You need to log in before you can comment on or make changes to this bug.