SecurityEngineering/ThirdPartyCookies: Difference between revisions

SecurityEngineering/ThirdPartyCookies (view source)

255 bytes removed , 26 February 2013

canmove, Confirmed users

1,537

edits

@@ Line 38: / Line 38: @@
 '''Will nightly/aurora be enough time to test this out?'''
-* Let's assume we land in time for 21. The merge for 21 is really soon,and so we will hold it back in nightly for 22.
+* This is standard for features with a full cycle in nightly.
-* If we use the #ifdef trick to autopref it off in Beta, we can more quickly push the bits out to everyone without changing the defaults.
+* Monitor and adjust.  support.mozilla.org is listening, discussing breakage in dev-privacy, and taking input.
-Then we can more easily ship a test pilot study to moar users (beta users, for example) to test it. This is much easier than packaging the patch up in a test pilot study (which may be next to impossible since this required C++ hacking). I say lets land it and let it ride the train.
+* Might hold it back if we can't measure telemetry, but the current target is 22; gives us 6 weeks on each channel.
-{{ResolutionBox|{{ok| should we let the code ride the trains, but change the default back (for easier test pilot deployment)?}}}}
+{{ResolutionBox|{{resolved|Targeting release 22 -- gives us 6 weeks on each channel of bake time with active monitoring.}}}}
 === King Making ===