Closed
Bug 828625
Opened 12 years ago
Closed 12 years ago
unthrottle FF18.0 for 10am PST Thurs Jan 10, 2013
Categories
(Release Engineering :: Release Requests, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: kmoir, Assigned: kmoir)
References
Details
Attachments
(1 file)
2.79 KB,
patch
|
bhearsum
:
review+
|
Details | Diff | Splinter Review |
Talked to bajaj in #release-drivers and she said they were targeting 10am PST tomorrow.
Assignee | ||
Comment 1•12 years ago
|
||
Attachment #700000 -
Flags: review?(bhearsum)
Comment 2•12 years ago
|
||
Comment on attachment 700000 [details] [diff] [review]
patch
Review of attachment 700000 [details] [diff] [review]:
-----------------------------------------------------------------
::: inc/config-dist.php
@@ -95,4 @@
> // )
> // );
> //
> -$productThrottling = array(
This list should be emptied out rather than deleted altogether. Looks fine otherwise.
Attachment #700000 -
Flags: review?(bhearsum) → review-
Assignee | ||
Comment 3•12 years ago
|
||
If you look at line 85 of config-dist.php there's already a
$productThrottling = array(
);
I think my previous patch was wrong add a new $productThrottling definition but it worked since it superceded the first definition. Thus this patch is okay.
Comment 4•12 years ago
|
||
(In reply to Kim Moir [:kmoir] from comment #3)
> If you look at line 85 of config-dist.php there's already a
>
> $productThrottling = array(
> );
>
> I think my previous patch was wrong add a new $productThrottling definition
> but it worked since it superceded the first definition. Thus this patch is
> okay.
That's the commented out one, isn't it?
Comment 5•12 years ago
|
||
(In reply to Kim Moir [:kmoir] from comment #3)
> I think my previous patch was wrong add a new $productThrottling definition
> but it worked since it superceded the first definition. Thus this patch is
> okay.
This explanation looks correct to me, as we lost the example in a comment in an earlier confusion. Lets try to avoid two declarations next time.
Assignee | ||
Comment 6•12 years ago
|
||
Yes :-) Line 85 isn't commented out, but isn't reflected in the patch.
Comment 7•12 years ago
|
||
(In reply to Kim Moir [:kmoir] from comment #1)
> Created attachment 700000 [details] [diff] [review]
> patch
Congratulations on attachment 700000 [details] [diff] [review]! And, uhh, your r-. :D
Comment 8•12 years ago
|
||
Comment on attachment 700000 [details] [diff] [review]
patch
Ah, I see now. Sorry about that - it's clear to me now after looking at the current, full state, of the file.
Attachment #700000 -
Flags: review- → review+
Updated•12 years ago
|
Assignee: nobody → kmoir
Assignee | ||
Updated•12 years ago
|
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Verified fixed using the following builds...
Windows 7:
----------
16.0.2 en-US -> 18.0 en-US partial
17.0 de -> 18.0 de complete+fallback
Mac OSX 10.7:
-------------
15.0.1 es-ES -> 18.0 es-ES partial+fallback
16.0 en-US -> 18.0 en-US complete
Ubuntu 12.04:
-------------
17.0 en-US -> 18.0 en-US complete
16.0.2 fr -> 18.0 fr partial+fallback
In all cases a background update was found, downloaded, and applied successfully.
Status: RESOLVED → VERIFIED
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•