** When re-enable updates for Aurora, update the bouncer locations for [https://bounceradmin.mozilla.com/admin/mirror/location/9380/ firefox-aurora-latest] (installer) and [https://bounceradmin.mozilla.com/admin/mirror/location/9717/ firefox-aurora-stub] (stub installer) to use the new version
** After bouncer update for nightly and aurora, check if disk space needs cleanup per {{bug|703559}}
== VCS Sync duties ==
* We *must* freeze the vcs-syncing of the B2G version migrating into (even gecko number) or out of (odd gecko number) Aurora.
** This is for gecko.git, and all gecko l10n.
** This can start syncing after we point vcs-sync at the new repo locations.
*** Even numbered Aurora: gecko.git version will move out of mozilla-central into mozilla-aurora
*** Even numbered Aurora: gecko l10n will all shift (central, aurora, beta, release all increment their minor version numbers)
*** Even numbered Aurora: gaia l10n will have a new set of hg repos for the stability version of b2g, and a new version number for master.
*** Odd numbered Aurora: gecko.git version will move out of mozilla-aurora into mozilla-b2gXX_v1_X
*** Odd numbered Aurora: gecko l10n will stay the same
Release Management will notify Release Engineering when the migration is about to happen; we need to be ready to perform this pause/reenable.
'''If we miss this freeze, we may be forced to perform a non-fastforwardable push on these repos, which will cause partner unhappiness.'''
= Next merge days =
