Bug 512085 (SM1.1.18)

tracking bug for build and release of SeaMonkey 1.1.18

RESOLVED FIXED

Status

SeaMonkey
Release Engineering
--
critical
RESOLVED FIXED
8 years ago
7 years ago

People

(Reporter: Robert Kaiser, Assigned: Robert Kaiser)

Tracking

({fixed-seamonkey1.1.18})

Trunk
fixed-seamonkey1.1.18
Dependency tree / graph
Bug Flags:
blocking-seamonkey1.1.18 +

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Assignee)

Description

8 years ago
+++ This bug was initially created as a clone of Bug #496355 +++
(Assignee)

Updated

8 years ago
Assignee: nobody → kairo
Flags: blocking-seamonkey1.1.18+
(Assignee)

Updated

8 years ago
Depends on: 506948
(Assignee)

Updated

8 years ago
Blocks: 512086
(Assignee)

Comment 1

8 years ago
For a good period of time leading up to this release, the "hoshi" box doing the 1.8 branch Linux builds and NATing the Windows machine was having problems due to a file system problem, which I fixed this afternoon Central European time.

Now that it should be up again, I started the process with tagging.


Tagging process started at 2009-08-22 11:48 PDT using the following commands:

cvs -d :ext:kairo%kairo.at@cvs.mozilla.org:/cvsroot checkout -r GECKO181_20090812_RELBRANCH -D "2009-08-22 20:48:00" mozilla/client.mk
cd mozilla
make -f client.mk checkout MOZ_CO_PROJECT=suite
rm -rf security/nss-fips
cvs -d :ext:kairo%kairo.at@cvs.mozilla.org:/cvsroot tag -b SEAMONKEY_1_1_18_MINIBRANCH client.mk
cvs -d :ext:kairo%kairo.at@cvs.mozilla.org:/cvsroot commit -r SEAMONKEY_1_1_18_MINIBRANCH -m 'initial minibranch commit' client.mk
mv client.mk ../client.mk.orig
sed 's/THUNDERBIRD_2_0_0_23_RELEASE/SEAMONKEY_1_1_18_RELEASE/' ../client.mk.orig > client.mk
rm ../client.mk.orig
cvs -d :ext:kairo%kairo.at@cvs.mozilla.org:/cvsroot commit -r SEAMONKEY_1_1_18_MINIBRANCH -m 'edit tags to pull from SEAMONKEY_1_1_18_RELEASE' client.mk
mv xpfe/bootstrap/version.txt ../version.txt.orig
sed 's/pre//' ../version.txt.orig > xpfe/bootstrap/version.txt
rm ../version.txt.orig
mv xpfe/bootstrap/module.ver ../module.ver.orig
sed 's/pre//' ../module.ver.orig > xpfe/bootstrap/module.ver
rm ../module.ver.orig
cvs -d :ext:kairo%kairo.at@cvs.mozilla.org:/cvsroot commit -r GECKO181_20090812_RELBRANCH -m 'remove "pre" postfix from SeaMonkey version on release branch' xpfe/bootstrap/module.ver xpfe/bootstrap/version.txt
cvs -d :ext:kairo%kairo.at@cvs.mozilla.org:/cvsroot tag -F SEAMONKEY_1_1_18_RELEASE client.mk
cvs -d :ext:kairo%kairo.at@cvs.mozilla.org:/cvsroot tag SEAMONKEY_1_1_18_RELEASE


Tagging finished at approx. 2009-08-22 12:00 PDT
No longer blocks: 512086
(Assignee)

Updated

8 years ago
Depends on: 512086
(Assignee)

Comment 2

8 years ago
Version bumped to 1.1.19pre on main 1.8 branch, waiting for a successful Linux nightly cycle before starting off the 1.1.18 release build runs.
(Assignee)

Comment 3

8 years ago
The builds are done and up at http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/candidates-1.1.18/ now - the funny thing is that the first green build hoshi did in weeks is the release :)
(Assignee)

Comment 4

8 years ago
Now that we have a patch for bug 512187, I landed it on the relbranch, moved the SEAMONKEY_1_1_18_RELEASE tag on that file and restarted Windows builds.
I think I won't renew the source tarballs for this as those using the tarballs are usually not using the Windows installer.
(Assignee)

Updated

8 years ago
Alias: SM1.1.18
(Assignee)

Updated

8 years ago
Depends on: 514394
(Assignee)

Comment 5

8 years ago
Testing seems enough and no problems reported since I posted the renewed Windows builds. Therefore, I pushed the files to public FTP now, official release should follow in a few hours.
(Assignee)

Comment 6

8 years ago
Website changes pushed online, we can consider this done.
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
(Assignee)

Updated

8 years ago
Keywords: fixed-seamonkey1.1.18
(Assignee)

Updated

7 years ago
Component: Project Organization → Release Engineering
(Assignee)

Updated

7 years ago
QA Contact: organization → release
You need to log in before you can comment on or make changes to this bug.