Closed Bug 640510 Opened 9 years ago Closed 7 years ago

Close previous Hg branch when starting a new one

Categories

(Release Engineering :: Release Automation: Other, enhancement, P5)

enhancement

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: sgautherie, Unassigned)

References

Details

(Whiteboard: [automation])

(m-c) Bug 611030 (and (c-c) bug 631902) did it once manually.

This bug is to investigate automating
{
hg update -r <previous branch name>
hg commit --close-branch -m "Bug <nnn>; Closing old branch that is no longer used."

hg update -r default  [Or whatever needs to be done next, if any.]
}

This should happen if the previous branch is not yet closed only: not for each build tag before release of the new branch.
Blocks: 563818
You're referring specifically to relbranches, correct?
I guess so (though I don't know all details about this):
'*_*_RELBRANCH' branches that are used to release new (minor) application versions.
See blocking bugs for examples of such branches.
Blocks: 627271
Priority: -- → P5
Mass move of bugs to Release Automation component.
Component: Release Engineering → Release Engineering: Automation (Release Automation)
No longer blocks: hg-automation
This is so low priority that we're never going to get around to doing it. It's possible we may even get rid of relbranches altogether.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.