SecurityEngineering/Public Key Pinning/SiteOperators: Difference between revisions

SecurityEngineering/Public Key Pinning/SiteOperators (view source)

45 bytes added , 27 May 2014

Confirmed users

238

edits

@@ Line 4: / Line 4: @@
 == How much notice do I need to give for pinset changes? ==
-Firefox is on a 6-week cycle, with 4 different trains: Nightly, Aurora, Beta, Release. For the next merge date, please see [[RapidRelease/Calendar]].
+Firefox is on a 6-week cycle, with 4 different trains: Nightly, Aurora, Beta, Release. For the next merge date, please see [[RapidRelease/Calendar]]. We prefer not to make changes once Firefox is in Beta, and the current lifetime of the pinset in Release is 8 weeks. Therefore we need at least 14 weeks notice for any pinset changes, preferably 20.
-Ideally we'd like to have 18 weeks notice before any pinset changes, in order to have adequate time for testing and uplifting (if necessary) to Aurora.
 weeks is the absolute minimum amount of time we need to make changes.