721885 - Shut off shadow-central

Status: RESOLVED FIXED

(Release Engineering :: General, defect, P2)

Description

[Chris AtLee [:catlee]]

The last push here was nov 2010, and I believe the only other pushes were regular merges from m-c.

Comment 1

[Daniel Veditz [:dveditz]]

Rapid Release certainly took a lot of wind out of shadow-central's sails. best case it only bought us a month or two of obfuscation.

As a hidden-testcase repo it had more promise, I'll check with engineering whether they want to use it for that.

Comment 2

[Chris AtLee [:catlee]]

Attachment: turn off shadow-central

Comment 3

[[e-mail] (:bhearsum)]

Comment on attachment 601311 [details] [diff] [review]
turn off shadow-central

Review of attachment 601311 [details] [diff] [review]:
-----------------------------------------------------------------

Looks good. There's some references to shadow-central in misc.py that you might want to remove (not sure). We should definitely remove it from production-branches.json though.

Comment 4

[John O'Duinn [:joduinn] (please use "needinfo?" flag)]

Found in triage, moving to new component

Comment 5

[Chris AtLee [:catlee]]

Last call here - I'd like to shut this off this week if possible.

Comment 6

[Daniel Veditz [:dveditz]]

mail sent to the security-group asking for feedback.

Comment 7

[Alex Keybl [:akeybl]]

Let's hold on this until we do a postmortem for FF11 and understand whether shadow-central may have prevented knowledge of bug 735104.

Comment 8

[Daniel Veditz [:dveditz]]

There have been no objections to shutting this off (some regrets, but the benefits don't outweigh the costs in the Rapid Release model).

Comment 9

[[e-mail] (:bhearsum)]

Made it to production just now.