Closed
Bug 593828
Opened 15 years ago
Closed 15 years ago
Add SeaMonkey 2.0.7 to bouncer
Categories
(Release Engineering :: General, defect, P1)
Release Engineering
General
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: kairo, Assigned: armenzg)
References
Details
(Time runs fast, just realized that Sept 7 is tomorrow and I haven't filed this yet...)
The SeaMonkey team is preparing an update, SeaMonkey 2.0.7 (to go public in sync with Firefox 3.5.12), and once again, we'd like to have the builds added to bouncer for downloads.
The relevant URLs to add are (bouncer and FTP):
http://download.mozilla.org/?product=seamonkey-2.0.7&os=win&lang=en-US
http://releases.mozilla.org/pub/mozilla.org/seamonkey/releases/2.0.7/win32/en-US/SeaMonkey%20Setup%202.0.7.exe
http://download.mozilla.org/?product=seamonkey-2.0.7&os=linux&lang=en-US
http://releases.mozilla.org/pub/mozilla.org/seamonkey/releases/2.0.7/linux-i686/en-US/seamonkey-2.0.7.tar.bz2
http://download.mozilla.org/?product=seamonkey-2.0.7&os=osx&lang=en-US
http://releases.mozilla.org/pub/mozilla.org/seamonkey/releases/2.0.7/mac/en-US/SeaMonkey%202.0.7.dmg
http://download.mozilla.org/?product=seamonkey-2.0.7-complete&os=win&lang=en-US
http://releases.mozilla.org/pub/mozilla.org/seamonkey/releases/2.0.7/update/win32/en-US/seamonkey-2.0.7.complete.mar
http://download.mozilla.org/?product=seamonkey-2.0.7-complete&os=linux&lang=en-US
http://releases.mozilla.org/pub/mozilla.org/seamonkey/releases/2.0.7/update/linux-i686/en-US/seamonkey-2.0.7.complete.mar
http://download.mozilla.org/?product=seamonkey-2.0.7-complete&os=osx&lang=en-US
http://releases.mozilla.org/pub/mozilla.org/seamonkey/releases/2.0.7/update/mac/en-US/seamonkey-2.0.7.complete.mar
http://download.mozilla.org/?product=seamonkey-2.0.7-partial-2.0.6&os=win&lang=en-US
http://releases.mozilla.org/pub/mozilla.org/seamonkey/releases/2.0.7/update/win32/en-US/seamonkey-2.0.6-2.0.7.partial.mar
http://download.mozilla.org/?product=seamonkey-2.0.7-partial-2.0.6&os=linux&lang=en-US
http://releases.mozilla.org/pub/mozilla.org/seamonkey/releases/2.0.7/update/linux-i686/en-US/seamonkey-2.0.6-2.0.7.partial.mar
http://download.mozilla.org/?product=seamonkey-2.0.7-partial-2.0.6&os=osx&lang=en-US
http://releases.mozilla.org/pub/mozilla.org/seamonkey/releases/2.0.7/update/mac/en-US/seamonkey-2.0.6-2.0.7.partial.mar
| Assignee | ||
Comment 1•15 years ago
|
||
Working on it.
Kairo could you be watchful of the priority flag? If there is a priority set it won't show up on the releng-triage queue and might add can increase chances of not being seen. Instead you can use the critical flag.
Assignee: nobody → armenzg
Severity: normal → blocker
Status: NEW → ASSIGNED
Priority: P2 → P1
| Assignee | ||
Comment 2•15 years ago
|
||
Kairo can you please verify that this is working?
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
| Reporter | ||
Comment 3•15 years ago
|
||
(In reply to comment #2)
> Kairo can you please verify that this is working?
I'm always doing that once the build have been pushed (before that, I can't really test).
And good to know about the priority, I hope I'll remember - I'm always cloning those bugs, which copies the priority from the old one.
| Assignee | ||
Comment 4•15 years ago
|
||
For reference and for following requests, the right format to provide to a releng is the following:
Any of the entries in comment#0 should be like this:
/seamonkey/releases/2.0.7/win32/:lang/SeaMonkey%20Setup%202.0.7.exe
instead of like this:
http://releases.mozilla.org/pub/mozilla.org/seamonkey/releases/2.0.7/win32/en-US/SeaMonkey%20Setup%202.0.7.exe
To be more explicit the difference is:
* strip "http://releases.mozilla.org/pub/mozilla.org"
* substitute "en-US" to ":lang"
BTW do you know if there is a way a releng can check that the entry was correct?
Comment 6•15 years ago
|
||
(In reply to comment #4)
> BTW do you know if there is a way a releng can check that the entry was
> correct?
I often look at uptake when we start to get mirrors with all platforms, when it's fairly easy to spot the one entry you goofed on. Not aware of anyway prior to that.
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•