Closed Bug 682739 Opened 9 years ago Closed 9 years ago
Tracking bug for build and release of Sea
Monkey 2 .3 .3 MU [Major Update]
+++ This bug was initially created as a clone of Bug #668741 +++ For SeaMonkey 2.3.1 we want Major Updates to come from 1.9.1 (SeaMonkey 2.0) This bug is intended to track that.
This fixes the patched-config up.
Attachment #556430 - Flags: feedback?(kairo)
Comment on attachment 556430 [details] [diff] [review] patcher-config I have not checked every detail, but it looks good overall to me.
Attachment #556430 - Flags: feedback?(kairo) → feedback+
Pushed config changes: http://hg.mozilla.org/build/buildbot-configs/rev/b0273eaf9e02 and checked in cvs changes: $ cvs commit -m "Bug 682739, SeaMonkey 2.0.14 -> SeaMonkey 2.3.1 Major Update" cvs commit: Examining . Checking in moz191-seamonkey-branch-major-patcher2.cfg; /cvsroot/mozilla/tools/patcher-configs/moz191-seamonkey-branch-major-patcher2.cfg,v <-- moz191-seamonkey-branch-major-patcher2.cfg new revision: 1.11; previous revision: 1.10 done
Had to |ln -s macosx64_info.txt macosx_info.txt| in our 2.3.1 candidates dir
the symlink for macosx64_info.txt -> macosx_info.txt was created as part of the 2.3.3 automation now. Did cvs commit for 2.3.3 patcher config $ cvs ci -m "Update SeaMonkey Major Update config" cvs commit: Examining . Checking in moz191-seamonkey-branch-major-patcher2.cfg; /cvsroot/mozilla/tools/patcher-configs/moz191-seamonkey-branch-major-patcher2.cf g,v <-- moz191-seamonkey-branch-major-patcher2.cfg new revision: 1.13; previous revision: 1.12 done And hg commit for buildbot config. (http://hg.mozilla.org/build/buildbot-configs/rev/b1d6d34bcde6) Reconfigured buildmaster and triggered through web UI.
Summary: Tracking bug for build and release of SeaMonkey 2.3.1 MU [Major Update] → Tracking bug for build and release of SeaMonkey 2.3.3 MU [Major Update]
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.