Closed Bug 654860 Opened 15 years ago Closed 15 years ago

unthrottle MU from 3.5.19/3.6.17 -> 4.0.1

Categories

(Release Engineering :: General, defect, P1)

x86
All
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: joduinn, Assigned: catlee)

Details

Attachments

(1 file)

(Couldnt find bug for this - even though we've talked about this for weeks - so filing. please DUP-me if one exists.) Plan is to do prompt MU from: * FF3.5.19 --> FF4.0.1 * FF3.6.17 --> FF4.0.1 Current schedule is to do this tomorrow (thurs, 05may)
I'll write the patch for this, but go is 10-1ish PDT, so I'll need someone else to land and deploy.
This removes the throttling on the 4.0.1 MU and sets up for future releases, although by all accounts it will take a chemspill for there to be a 3.5.20. We can always that part again later.
Attachment #530223 - Flags: review?(catlee)
*remove that part later.
Attachment #530223 - Flags: review?(catlee) → review+
OK, this is ready for landing, tagging and deployment. I don't want to do the first two several hours before the last, and the push time is not NZST friendly, so over to EDT/PDT folk.
Assignee: nobody → catlee
Priority: -- → P1
Comment on attachment 530223 [details] [diff] [review] [cvs] Move throttling to 3.5.20 & 3.6.18 [catlee] aus/xml/inc:1% cvs commit cvs commit: Examining . Checking in config-dist.php; /cvsroot/mozilla/webtools/aus/xml/inc/config-dist.php,v <-- config-dist.php new revision: 1.140; previous revision: 1.139 done [catlee] aus/xml/inc% cvs tag -F AUS2_PRODUCTION config-dist.php T config-dist.php
Attachment #530223 - Flags: checked-in+
This was deployed via a request to bkero on IRC. QA has signed off.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: