My Firefox Developer Edition hasn't updated from buildID 20141128004001 even after repeatedly opening the about dialog. It's stuck in rev 390a34a40ea4 even though I see 3 more pushes in the aurora branch and the corresponding nightly builds on the FTP server. Manually retrieving the same update.xml confirms this: $ curl "https://aus4.mozilla.org/update/3/Firefox/35.0a2/20141128004001/Linux_x86_64-gcc3/en-US/aurora/Linux%203.16.0-25-generic%20(GTK%202.24.25)/default/default/update.xml?force=1" <?xml version="1.0"?> <updates> </updates> Did we miss a step in last week's branching procedure?
Nope, seem to have done the step that's always a part of merging to aurora, "completely disable updates locking them to a rev before the merge, until QA has run smoketests on the new aurora and told relman to tell releng to unthrottle it." Dunno if relman has any documentation of anything, but releng's docs on being told to shut them off (which is now done automatically) and then being told to turn them back on are in https://wiki.mozilla.org/index.php?title=ReleaseEngineering/How_To/Enable_or_Disable_Updates_on_Aurora
Oh, that's good to know. I'm assuming that process is being followed then and I was just being impatient. Feel free to close the bug if that is the case, or I will close it myself once I start receiving updates again.
(In reply to Panos Astithas [:past] from comment #2) > Oh, that's good to know. I'm assuming that process is being followed then > and I was just being impatient. Feel free to close the bug if that is the > case, or I will close it myself once I start receiving updates again. The updates will get re-enabled after QE finishes validating the uplifted code. Maybe this week, but maybe not until next. (Resolving INVALID because this is just part of the normal process - there's nothing here we need to track.) Lawrence, I wonder if we need better communication around this now that we've moved Aurora to Developer Edition?
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → INVALID
Good idea Ben. The process is in place to ensure that Aurora/Dev Edition is good after the merge before pushing updates. The delay is due to release and beta1 activities, which also require verification. (This is something that I think we should review if we're going to continue to grow the Dev Edition audience size.)
Component: General Automation → General
Product: Release Engineering → Release Engineering
You need to log in before you can comment on or make changes to this bug.