tracking bug for build and release of SeaMonkey 2.0 Alpha 1

RESOLVED FIXED in seamonkey2.0a1

Status

defect
P1
critical
RESOLVED FIXED
11 years ago
9 years ago

People

(Reporter: kairo, Assigned: kairo)

Tracking

Trunk
seamonkey2.0a1
Dependency tree / graph
Bug Flags:
blocking-seamonkey2.0a1 +

Firefox Tracking Flags

(Not tracked)

Details

()

Attachments

(5 attachments)

No description provided.
Flags: blocking-seamonkey2.0a1+
As of right now, all three platforms are building.
Depends on: 450205
I wonder if version.txt should have gotten a "2.0a1" value, between "2.0a1pre" and "2.0a2pre" ?
Since KaiRo attached his log, might as well attach mine. (might inform choices for future releases)
Attachment #340268 - Attachment mime type: application/octet-stream → text/plain
Attachment #340235 - Attachment is patch: false
Fwiw (for next time), I wrote iirc that I think KaiRo's 430:1fcc1929e960 should have been a true backout+merge;
and version handling would have been 2 separate updates (never reverted).
We still have lots to learn here, and the next time we might have a more automated process (at least I hope we do), but thanks for the input, there are parts of that i already realized but I'm getting more experience in that as I go. ;-)

That said, builds are spinning again (started about half an hour ago), and I think I'll go to bed and continue with this stuff tomorrow, when the builds are hopefully done.
Priority: -- → P1
Posted file raw Linux build log
Posted file Windows build log
I've shortened the Windows build log to exclude all the duplicate build attempts I needed to finally get palmsync in correctly, so that the bzip2ed log fits the 512K size constraint of Bugzilla.
Unfortunately, Mac is still 515K after doing this.
Posted file Mac build log
Attachment #340431 - Attachment is patch: false
Attachment #340431 - Attachment mime type: text/plain → application/x-tar
OK, there's a mad trick in Bugzilla that allows such an oversized file getting in :p
Depends on: 457128
Depends on: 457379
...and it's publicly released!
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Congratulations ! :-)
Depends on: 459462
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.