Closed
Bug 640510
Opened 14 years ago
Closed 12 years ago
Close previous Hg branch when starting a new one
Categories
(Release Engineering :: Release Automation: Other, enhancement, P5)
Release Engineering
Release Automation: Other
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.
Comment 1•14 years ago
|
||
You're referring specifically to relbranches, correct?
Reporter | ||
Comment 2•14 years ago
|
||
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.
Updated•13 years ago
|
Blocks: hg-automation
Comment 3•13 years ago
|
||
Mass move of bugs to Release Automation component.
Component: Release Engineering → Release Engineering: Automation (Release Automation)
Updated•13 years ago
|
No longer blocks: hg-automation
Comment 4•12 years ago
|
||
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: 12 years ago
Resolution: --- → WONTFIX
Assignee | ||
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•