Closed
Bug 749877
Opened 13 years ago
Closed 13 years ago
Please throttle updates to FF13 beta 1 100%
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: akeybl, Unassigned)
References
Details
Attachments
(2 files)
|
(deleted),
patch
|
Details | Diff | Splinter Review | |
|
(deleted),
patch
|
rail
:
review+
mozilla
:
checked-in+
|
Details | Diff | Splinter Review |
Please throttle updates to FF13 beta 1 100%, such that only manual updates are available until we can figure out what to do about bug 749648.
|
||
Comment 1•13 years ago
|
||
Not entirely sure about this, but using this "throttle 5.0b1" patch as an example:
http://bonsai.mozilla.org/cvsview2.cgi?diff_mode=context&whitespace_mode=show&file=config-dist.php&branch=&root=/cvsroot&subdir=mozilla/webtools/aus/xml/inc&command=DIFF_FRAMESET&rev1=1.136&rev2=1.137
Looking for a reviewer.
|
|
||
Comment 2•13 years ago
|
||
Hm,
"throttle updates to 5.0b2 to 10%, r=catlee"
http://bonsai.mozilla.org/cvsview2.cgi?diff_mode=context&whitespace_mode=show&file=config-dist.php&branch=&root=/cvsroot&subdir=mozilla/webtools/aus/xml/inc&command=DIFF_FRAMESET&rev1=1.143&rev2=1.144
I think I need to throttle everything *before* 13.
|
|
||
Comment 3•13 years ago
|
||
I *think* this is it, but again not certain.
Attachment #619243 -
Flags: review?
|
||
Comment 4•13 years ago
|
||
Comment on attachment 619243 [details] [diff] [review]
throttle everything before 13
lgtm
Attachment #619243 -
Flags: review? → review+
|
|
||
Comment 5•13 years ago
|
||
Comment on attachment 619243 [details] [diff] [review]
throttle everything before 13
Checking in config-dist.php;
/cvsroot/mozilla/webtools/aus/xml/inc/config-dist.php,v <-- config-dist.php
new revision: 1.207; previous revision: 1.206
done
Attachment #619243 -
Flags: checked-in+
|
|
||
Updated•13 years ago
|
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
|
Assignee | |
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•