Try's slowing down and currently has 2723 heads, compared to 8 on mozilla-central so a trim of those older heads would be great.

So we need to know if this is something that can be done without a repo reset - and to find this out I propose that we: * schedule a 4 hour downtime and alert the stakeholders (via dev.planning/tree-management) about this downtime * attempt to trim heads on the live repo * do some test pushes * if it works, great and if it doesn't we reset the repo in this downtime window Thoughts? Questions? Concerns?

(In reply to comment #0) > Try's slowing down and currently has 2723 heads, compared to 8 on > mozilla-central so a trim of those older heads would be great. Today's try reset took care of the immediate issue. https://bugzilla.mozilla.org/show_bug.cgi?id=633161 is where we'll continue investigation of pruning heads on a live repo