Build:ReleasePolicy

Exactly *when* we ship depends on the product, and the *type* of release we are shipping. This question comes up at least once every release, so here's the official source-of-truth:

• For FF and TB zero-day exploit security releases:
  • when QA gives signoff
  • any time of day
  • any day
  • when the mirror uptake is enough to handle the traffic without melting any specific mirror. Rather then waiting fixed time, we monitor uptake with AUS owners until it is safe to ship.
  • IT will monitor traffic, and if needed use AUS-throttle to prevent meltdown.

• For FF regular scheduled security/update dot-releases:
  • when QA gives signoff
  • after 3pm PST (when Europe traffic low)
  • not on Monday (because of corporate sysadmins)
  • not on Friday (in case something goes wrong, and we have to fix it Saturday)

• For TB regular scheduled security/update dot-releases:
  • when QA gives signoff
  • anytime of day (traffic hit is small enough)
  • not on Monday
  • not on Friday

• For FF and TB alpha/beta/rc
  • QA gives signoff
  • anytime of day (traffic hit is small enough)
  • any day of week

• For FF major releases:
  • give IT a few weeks advance notice to ramp up additional bandwidth
  • when QA gives signoff
  • after 3pm PST
  • not on Monday, Friday

• For TB major releases:
  • when QA gives signoff
  • after 3pm PST
  • not on Monday, Friday

• There was a tradition of only releasing on Tues/Thurs. This was because of bandwidth restrictions, and is no longer valid with the enhanced infrastructure.