Closed
Bug 931832
Opened 11 years ago
Closed 11 years ago
Disable aurora daily updates (26) until merge to mozilla-aurora has stabilized
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: lsblakk, Assigned: rail)
References
Details
Attachments
(2 files)
3.60 KB,
patch
|
rail
:
review+
hwine
:
checked-in+
|
Details | Diff | Splinter Review |
2.05 KB,
patch
|
hwine
:
review+
rail
:
checked-in+
|
Details | Diff | Splinter Review |
Please disable aurora daily updates (FF26) until merge to mozilla-aurora has stabilized.
Comment 1•11 years ago
|
||
Disable aurora->v1.2 branch in gecko.git for legacy system
Attachment #823389 -
Flags: review?(rail)
Assignee | ||
Comment 2•11 years ago
|
||
Attachment #823390 -
Flags: review?(hwine)
Assignee | ||
Updated•11 years ago
|
Attachment #823389 -
Flags: review?(rail) → review+
Comment 3•11 years ago
|
||
Comment on attachment 823390 [details] [diff] [review] disable aurora updates lgtm
Attachment #823390 -
Flags: review?(hwine) → review+
Assignee | ||
Comment 4•11 years ago
|
||
Comment on attachment 823390 [details] [diff] [review] disable aurora updates https://hg.mozilla.org/build/buildbot-configs/rev/ab36e83d7fcb
Attachment #823390 -
Flags: checked-in+
Comment 5•11 years ago
|
||
For legacy conversion: http://hg.mozilla.org/users/hwine_mozilla.com/repo-sync-tools/rev/b6f5988f392e deployed to all production boxes conversion process restarted updates for v1.2 to gecko.git now disabled on legacy
Updated•11 years ago
|
Attachment #823389 -
Flags: checked-in+
Assignee | ||
Comment 6•11 years ago
|
||
in production
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Setting Tracy as QA Contact for Firefox 26 to verify Aurora updates are disabled.
QA Contact: rail → twalker
Assignee | ||
Comment 8•11 years ago
|
||
Just to be clear. The updates are not disabled, they are pointing and will be pointing to the current update (20121028xxx) until we re-enable the updates.
Comment 9•11 years ago
|
||
Thanks for the clarification, Rail. A build from 20131026 correctly updated to the 20131028 build. An update from that build is not found as expected. (normally would have updated to a build for 20131029)
Status: RESOLVED → VERIFIED
Updated•10 years ago
|
QA Contact: twalker
You need to log in
before you can comment on or make changes to this bug.
Description
•