Close obsolete heads on mozilla-beta and mozilla-release

RESOLVED FIXED

Status

Developer Services
Mercurial: hg.mozilla.org
RESOLVED FIXED
2 years ago
2 years ago

People

(Reporter: RyanVM, Unassigned)

Tracking

Details

(Reporter)

Description

2 years ago
Both branches have a lot of old heads on them for various releases that have long-since shipped. We should close them out.

Comment 1

2 years ago
See bug 927219 for the chaos the last time we did this. I don't think beta and release were that huge of a problem, however. We /may/ want to coordinate doing this as part of the next uplift. Even better is if we could have the uplift mechanism close old release branches as part of the uplift. Or even during the branching itself - the branches usually don't need to exist for very long.

I hate the release branches.
Depends on: 927219
JFYI, the new release automation (AKA build promotion, in progress) won't be tagging/branching gecko repos \o/

Comment 3

2 years ago
I just closed out a bunch of old release branches on the beta repo.

https://hg.mozilla.org/releases/mozilla-beta/pushloghtml?changeset=a86835580095

For posterity, the commands I used were something like the following:

for b in `hg branches | awk '{print $2, $1}' | sort | awk '{print $2}' | grep -v default`; do echo $b; hg up $b; hg commit --close-branch -m "Bug 1249802 - Close old branch $b" -d '1464988859 0'; done

for node in `hg log -r '324515:' -T '{node}\n'`; do hg debugsetparents . $node; hg commit -m 'Bug 1249802 - Merge closed branch head into default'; done
:gps,

Would you consider this bug resolved?
Flags: needinfo?(gps)

Comment 5

2 years ago
Yes.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Flags: needinfo?(gps)
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.