Closed Bug 668734 Opened 13 years ago Closed 13 years ago

Add SeaMonkey 2.2 [final release] to bouncer

Categories

(Release Engineering :: General, defect, P2)

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: Callek, Assigned: nthomas)

References

Details

+++ This bug was initially created as a clone of Bug #668733 +++ +++ This bug was initially created as a clone of Bug #667494 +++ +++ This bug was initially created as a clone of Bug #647930 +++ The SeaMonkey team is preparing the final build of the next release series, SeaMonkey 2.2, and once again, we'd like to have the builds added to bouncer for downloads. We need to do a full set of builds, since 2.2 final [unlike 2.2b3] will be off the -release repo's rather than the -beta repo's. The relevant URL snippets for the entries to add are (bouncer and FTP): ?product=seamonkey-2.2&os=win /seamonkey/releases/2.2/win32/:lang/SeaMonkey%20Setup%202.2.exe ?product=seamonkey-2.2&os=linux /seamonkey/releases/2.2/linux-i686/:lang/seamonkey-2.2.tar.bz2 ?product=seamonkey-2.2&os=osx /seamonkey/releases/2.2/mac/:lang/SeaMonkey%202.2.dmg ?product=seamonkey-2.2-complete&os=win /seamonkey/releases/2.2/update/win32/:lang/seamonkey-2.2.complete.mar ?product=seamonkey-2.2-complete&os=linux /seamonkey/releases/2.2/update/linux-i686/:lang/seamonkey-2.2.complete.mar ?product=seamonkey-2.2-complete&os=osx /seamonkey/releases/2.2/update/mac/:lang/seamonkey-2.2.complete.mar product=seamonkey-2.2-partial-2.2b3&os=win /seamonkey/releases/2.2/update/win32/:lang/seamonkey-2.2b3-2.2.partial.mar ?product=seamonkey-2.2-partial-2.2b3&os=linux /seamonkey/releases/2.2/update/linux-i686/:lang/seamonkey-2.2b3-2.2.partial.mar ?product=seamonkey-2.2-partial-2.2b3&os=osx /seamonkey/releases/2.2/update/mac/:lang/seamonkey-2.2b3-2.2.partial.mar Bouncer monitors locale `tr` which will in this release.
Blocks: 668737
Assignee: nobody → nrthomas
Priority: -- → P2
Added.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.