Closed
Bug 556939
Opened 14 years ago
Closed 14 years ago
FF3.5.8 still throttled at 50%
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: joduinn, Assigned: bhearsum)
References
Details
Attachments
(1 file)
708 bytes,
patch
|
morgamic
:
review+
bhearsum
:
checked-in+
|
Details | Diff | Splinter Review |
As part of the FF3.5.8 release, we were asked to have these updates throttled to 50%. iirc it was because there were other releases going on the same time, and there was concerns about overloading infrastructure. While working on a different release, I noticed that FF3.5.8 is still throttled: mozilla/webtools/aus/xml/inc/config-dist.php $productThrottling = array( 'Firefox' => array( '3.0.19' => 0, '3.5.8' => 50, '3.5.9' => 0, '3.5.10' => 0 Now that initial load has died down, can we unthrottle this?
Yes, we should be able to unthrottle. Google was happy with the 50% and saw no additional/abnormal load on the servers.
Assignee | ||
Updated•14 years ago
|
Assignee: nobody → bhearsum
Assignee | ||
Comment 2•14 years ago
|
||
Attachment #437009 -
Flags: review?(morgamic)
Comment 3•14 years ago
|
||
Comment on attachment 437009 [details] [diff] [review] remove 3.5.8 throttling completely Looks good. Removes throttling for 3.5.8.
Attachment #437009 -
Flags: review?(morgamic) → review+
Assignee | ||
Comment 4•14 years ago
|
||
Comment on attachment 437009 [details] [diff] [review] remove 3.5.8 throttling completely Checking in config-dist.php; /cvsroot/mozilla/webtools/aus/xml/inc/config-dist.php,v <-- config-dist.php new revision: 1.70; previous revision: 1.69 done Tagged all of webtools/aus with AUS2_RTM_201004051003 and moved the AUS2_PRODUCTION tag on config-dist.php to rev 1.70: W config-dist.php : AUS2_PRODUCTION already exists on version 1.69 : NOT MOVING tag to version 1.70 foo-ix-blah:inc bhearsum$ cvs tag -F AUS2_PRODUCTION config-dist.php T config-dist.php
Attachment #437009 -
Flags: checked-in+
Assignee | ||
Comment 5•14 years ago
|
||
IT pushed this last night.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
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
•