Closed Bug 949154 Opened 6 years ago Closed 6 years ago

Need new Venkman, Chatzilla and DOM Inspector branches

Categories

(SeaMonkey :: Build Config, defect, blocker)

SeaMonkey 2.25 Branch
defect
Not set
blocker

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: mcsmurf, Assigned: mcsmurf)

Details

+++ This bug was initially created as a clone of Bug #937558 +++

The changeset from http://hg.mozilla.org/venkman/rev/f952b1852cd3 and the changeset from http://hg.mozilla.org/chatzilla/rev/6c225e18b126 need to be used on aurora, too, so we need new Venkman and Chatzilla branches.
Ian: Can you check if this is right what I did here? I used the commands from Bug 937558, changesets I used for the branch should be correct. If this is right, then I'll adjust client.py.

Created Venkman branch:
hg clone http://hg.mozilla.org/venkman -r f952b1852cd3 venkman_2_25
cd venkman_2_25
hg branch SEA2_25_RELBRANCH
hg commit -m "Bug 949154 - Created SeaMonkey 2.25 relbranch"
hg push --new-branch

Created Chatzilla branch:
hg clone http://hg.mozilla.org/chatzilla -r 6c225e18b126 chatzilla_2_25
cd chatzilla_2_25
hg branch SEA2_25_RELBRANCH
hg push --new-branch

Commits:
http://hg.mozilla.org/venkman/rev/113cafaf78d9
http://hg.mozilla.org/chatzilla/rev/c24671ae9594
Assignee: nobody → bugzilla
Looks fine, just wondering whether we need to do the same for DOM Inspector just to keep version numbers in sync.
Status: NEW → ASSIGNED
Added a new DOMI branch: http://hg.mozilla.org/dom-inspector/rev/2f3aa9849790
Also fixed that a directive was removed on 2.24 DOMI relbranch which should have only been removed in 2.25 relbranch as the underlying bug 939044 landed on Gecko 28/SeaMonkey 2.25: http://hg.mozilla.org/dom-inspector/rev/87599cab4bd2
Summary: Need new Venkman and Chatzilla branches → Need new Venkman, Chatzilla and DOM Inspector branches
Updated client.py on aurora: https://hg.mozilla.org/releases/comm-aurora/rev/27aad203310d
Updated client.py on trunk: https://hg.mozilla.org/comm-central/rev/60e32a30435d
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.