Per https://mail.mozilla.org/pipermail/firefox-dev/2016-July/004451.html, we want to retire fx-team. This bug will track that. The tentative plan is as follows: 1) (ASAP) Establish a whitelist of people who can push to fx-team. This will be sheriffs and people who have pushed to fx-team in the previous N days (I'm thinking 30). Everyone else will get an error message on push announcing the retirement of fx-team and instruct them to use Autoland or inbound. 2) (Optional) Prune the whitelist over time 3) Announce final day after which fx-team will be pushable 4) Make fx-team read-only on announced date jgriffin: are you OK with this plan?
Sounds good to me, sans objections from the Firefox team.
:gps: do you know the date when will be making fx-team read only and can disable the branch in buildbot-configs? Wondering because this could reduce our AWS spend (bug 1303152)
Per bug 1304864, we will make fx-team read-only on November 1.
At around 0004 UTC, fx-team became read-only by creating a .hg/readonlyreason file in the repository. An email follow-up will be sent shortly. In theory, references to fx-team can start being removed. However, I'd wait ~24h in case anything unexpected happens and we need to reopen the repo.