The weights of the mirrors have changed a lot since the days when we had volunteers, but we still expect 45k uptake for release builds. These days we have a little over 10k for updates, and 2 million for installers. (IT does it this way to get the behavior we want from bouncer, rather than anything else). We also don't need to make any distinction between uptake before notifying for 'ready for release' and 'ready to releasetest testing', since there is very short 'sync lag' between our CDN origin server and the CDN itself. Just 5 mins for the bouncer sentry to go around and request the files, and enable the CDN in bouncer.
Created attachment 8345199 [details] [diff] [review] [buildbotcustom] Change defaults to 10k See https://nagios.mozilla.org/sentry/ for the current weightings.
Created attachment 8345201 [details] [diff] [review] [buildbot-configs] Remove overrides from configs All these releases are the same from the point of view of serving them, CDN ftw.
It may be also related to bug 629648 and multiple reconfigs happened around that time.
I double checked emails for the last couple of cycles. We've gotten 'ready to release' builds for firefox esr17 and betas, where releasetestUptake was set to 1, and releaseUptake to 3, but not for release builds where the too-large defaults were used.
Comment on attachment 8345199 [details] [diff] [review] [buildbotcustom] Change defaults to 10k https://hg.mozilla.org/build/buildbotcustom/rev/1157a8772a53
Comment on attachment 8345201 [details] [diff] [review] [buildbot-configs] Remove overrides from configs https://hg.mozilla.org/build/buildbot-configs/rev/1dfba92bd2b6 I missed releasetestUptake settings in release-thunderbird-comm-esr24.py.template release-firefox-mozilla-release.py.template so I removed those at checkin too.
All done here?