Closed Bug 1343643 Opened 9 years ago Closed 9 years ago

Set Websense-related update rules for 52 release

Categories

(Release Engineering :: Release Requests, enhancement, P1)

enhancement

Tracking

(firefox52+ fixed)

RESOLVED FIXED
Tracking Status
firefox52 + fixed

People

(Reporter: lizzard, Assigned: bhearsum)

References

Details

We will need to set update rules for 52 release so that users on all previous versions of Firefox don't update to 52. We'll then tweak those rules later in the wek or the week after release, after some testing, to allow particular versions of websense through.
See Also: → 1342158
Priority: -- → P1
Assignee: nobody → bhearsum
This is related to bug 1329692 and bug 1342158. In addition to blocking all WebSense users from updating to 52.0 for a week, we want to blacklist the known bad versions documented in https://docs.google.com/spreadsheets/d/18n8NEimajNpnGRHdQsrrnyJ-Ufgvmpz-AXCUpVaFRMk/edit#gid=0
I've implemented these blocks on on the release-cdntest channel. The bad versions listed in https://docs.google.com/spreadsheets/d/18n8NEimajNpnGRHdQsrrnyJ-Ufgvmpz-AXCUpVaFRMk/edit#gid=0 will not update past their last supported release, and _no_ websense version will update past 51.0.1.
(In reply to Ben Hearsum (:bhearsum) from comment #2) > I've implemented these blocks on on the release-cdntest channel. The bad > versions listed in > https://docs.google.com/spreadsheets/d/18n8NEimajNpnGRHdQsrrnyJ-Ufgvmpz- > AXCUpVaFRMk/edit#gid=0 will not update past their last supported release, > and _no_ websense version will update past 51.0.1. Ended up moving these to release-localtest, because the in-flight 52.0 release meant that release-cdntest pointed to MARs that were 404s. The new version of the websense detector SystemAddon was deployed in bug 1342158 yesterday. We can probably remove the "(websense)" rule (id 449) once that has high uptake).
QA verified the release-localtest rules in https://bugzilla.mozilla.org/show_bug.cgi?id=1342158. I've moved them to release*, so we're now blocking known bad versions of WebSense on the release channel, and we have a rule in place to hold websense users on 51.0.1 when 52.0 ships.
The only thing left to do here is to remove the old rule that blocks all (websense) users from updating past 47.0.2.
(In reply to Ben Hearsum (:bhearsum) from comment #5) > The only thing left to do here is to remove the old rule that blocks all > (websense) users from updating past 47.0.2. I think we'll just leave this in place until we remove all of the WebSense rules.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.