Closed
Bug 523167
(SM2.0)
Opened 15 years ago
Closed 15 years ago
tracking bug for (build and) release of SeaMonkey 2.0 final
Categories
(SeaMonkey :: Release Engineering, defect, P1)
SeaMonkey
Release Engineering
Tracking
(Not tracked)
RESOLVED
FIXED
seamonkey2.0
People
(Reporter: kairo, Assigned: kairo)
References
()
Details
(Keywords: fixed-seamonkey2.0)
The builds have been done in bug 522409, we'll need to convert them to the final release, add the final release tags, etc. - https://wiki.mozilla.org/Releases/Firefox_3.5/BuildNotes has notes of how Mozilla people did this for their 3.5 final. Unfortunately we don't have automation for converting a RC to a final. And of course, that all bases on the assumption that RC2 is the final candidate, we hit no roadblocks in beta testing and can go gold with exactly those builds.
Flags: blocking-seamonkey2.0+
Assignee | ||
Updated•15 years ago
|
Alias: SM2.0
Assignee | ||
Comment 1•15 years ago
|
||
The builds have been renamed and internally staged, the buildmaster is prepared for running final tagging and source tarball generation.
Assignee | ||
Comment 2•15 years ago
|
||
tagging has been done, triggered building a new source tarball from that new SEAMONKEY_2_0_RELEASE tag.
Assignee | ||
Comment 3•15 years ago
|
||
OK, everything should be ready for a Tuesday release now, I'm targeting for 5am-6am Mozilla time (Pacific) on that day.
Assignee | ||
Comment 4•15 years ago
|
||
It's done!
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•15 years ago
|
Keywords: fixed-seamonkey2.0
Assignee | ||
Updated•14 years ago
|
Component: Project Organization → Release Engineering
Assignee | ||
Updated•14 years ago
|
QA Contact: organization → release
You need to log in
before you can comment on or make changes to this bug.
Description
•