Closed Bug 522409 (SM2.0rc2) Opened 15 years ago Closed 15 years ago

tracking bug for build and release of SeaMonkey 2.0 RC2

Categories

(SeaMonkey :: Release Engineering, defect)

Product:
SeaMonkey
Component:
Release Engineering
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

(Not tracked)

Status:
RESOLVED FIXED
Milestone:
seamonkey2.0

People

(Reporter: kairo, Assigned: kairo)

References

(
URL
)

Details

(Keywords: fixed-seamonkey2.0)

No description provided.
Flags: blocking-seamonkey2.0+
Updated shipped-locales in http://hg.mozilla.org/comm-central/rev/8c3a7a74702c We have 19 locales opted in and green for this last beta: be ca cs de es-AR es-ES fr gl hu ka lt nb-NO nl pl pt-PT ru sk sv-SE tr Source revisions to build: http://hg.mozilla.org/comm-central/rev/8c3a7a74702c http://hg.mozilla.org/releases/mozilla-1.9.1/rev/e178dbd2a389 http://hg.mozilla.org/dom-inspector/rev/f1fc2297e2c5 http://hg.mozilla.org/venkman/rev/74a705e85ad0 chatzilla CVS timestamp: 2009-10-14 00:00 Opted in L10n revisions are in http://hg.mozilla.org/build/buildbot-configs/file/f2e3d36bce2e/seamonkey/l10n-changesets Starting automated build process with those revisions in the next minutes.
We need to do a build2 along with FF 3.5.4 build 3. All trees that had no relbranchOverride now come from COMM1914_20091015_RELBRANCH All revisions are unchanged, except: http://hg.mozilla.org/comm-central/rev/acaa5081b109 http://hg.mozilla.org/releases/mozilla-1.9.1/rev/49342a1d9d93
Looking at Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.4) Gecko/20091016 SeaMonkey/2.0 off the ftp site, about:buildconfig tells me it was built from http://hg.mozilla.org/releases/mozilla-1.9.1/rev/e178dbd2a389 rather than http://hg.mozilla.org/releases/mozilla-1.9.1/rev/49342a1d9d93 (which doesn't have a SEAMONKEY tag). Possibly caused by Firefox tagging in http://hg.mozilla.org/releases/mozilla-1.9.1/rev/2fe392234f8c removing them?
Builds for build2 are available from http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/2.0rc2-candidates/build2/ rsx11m: Ugh, you might be right. If so, I need to redo all builds :(
See https://wiki.mozilla.org/Releases/Firefox_3.5.4/BuildNotes#Tag_3 on what Firefox did. The seamonkey-2.0rc2.source.tar.bz2 sources contain the latest patch checked in on 1.9.1, but they were built in the small window between seabld setting the SM tags and ffxbld removing them, thus hard to tell.
Right, Firefox tagging messed up everything, recovering from the race condition didn't work as well as expected, and I didn't check it closely enough even though we were discussing about the race condition in the build channel. Cleaning buildslaves in preparation for a build 3, which I'll start off in a moment. I already gave up frowning.
Ok, about:buildconfig of the unsigned Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.4) Gecko/20091017 SeaMonkey/2.0 (build3) now correctly refers to http://hg.mozilla.org/releases/mozilla-1.9.1/rev/49342a1d9d93 instead.
That's the new one from build3 now, right?
Yes, as stated in comment #8. ;-)
Ah, I overlooked that statement. Thanks for verifying this, I already feel a bit better. :)
Depends on: 521220, 521397
Depends on: 522899
The builds are now available on http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/2.0rc2-candidates/build3/ - the updates are live on the betatest channel.
Files have been pushed to the public releases directory, waiting for mirrors to sync.
Mirror saturation OK, push to website done.
website has updated, announcements are posted, updates pushed on the beta channel, it's done.
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Keywords: fixed-seamonkey2.0
Component: Project Organization → Release Engineering
QA Contact: organization → release
You need to log in before you can comment on or make changes to this bug.