Bug 523167 (SM2.0)

tracking bug for (build and) release of SeaMonkey 2.0 final

RESOLVED FIXED in seamonkey2.0

Status

SeaMonkey
Release Engineering
P1
critical
RESOLVED FIXED
9 years ago
8 years ago

People

(Reporter: Robert Kaiser, Assigned: Robert Kaiser)

Tracking

({fixed-seamonkey2.0})

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

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Assignee)

Description

9 years ago
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

9 years ago
Alias: SM2.0
(Assignee)

Updated

9 years ago
Depends on: 524145
(Assignee)

Updated

9 years ago
Depends on: 524146
(Assignee)

Comment 1

9 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

9 years ago
tagging has been done, triggered building a new source tarball from that new SEAMONKEY_2_0_RELEASE tag.
(Assignee)

Comment 3

9 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

9 years ago
It's done!
Status: ASSIGNED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED
(Assignee)

Updated

9 years ago
Keywords: fixed-seamonkey2.0
(Assignee)

Updated

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

Updated

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