Closed Bug 405255 Opened 17 years ago Closed 17 years ago

change in-code URLs to new SeaMonkey website

Categories

(SeaMonkey :: General, defect)

defect
Not set
trivial

Tracking

(Not tracked)

RESOLVED FIXED
seamonkey2.0a1

People

(Reporter: kairo, Assigned: kairo)

Details

(Keywords: fixed-seamonkey1.1.8)

Attachments

(4 files)

We're referring to the SeaMonkey web pages in many places in the code, we should change those places to the new www.seamonkey-project.org - even though the redirects work fine, it's better to directly go to the new website in new releases.
Here's the trunk patch. This is more or less just a search-and-replace, with exception of correcting the URL in the README to the right target and changing the not-yet-used update server to aus2-community per bug 381420 so we hopefully have the right URL when finally activating AUS.
Attachment #290524 - Flags: superreview?(neil)
Attachment #290524 - Flags: review?(neil)
Attached patch branch patchSplinter Review
...and here's a branch patch as well. Note that I'm not fully sold yet that we should do those changes to locale strings when we are in a quite strict locale freeze and redirects are working well for the old URLs, but I'll leave that decision up to you.
Attachment #290528 - Flags: superreview?(neil)
Attachment #290528 - Flags: review?(neil)
Attachment #290528 - Flags: approval-seamonkey1.1.8?
Comment on attachment 290524 [details] [diff] [review]
trunk patch: change all URLs to new website

> # update notifications: new update page
>-update_notifications.provider.0.datasource=http://www.mozilla.org/projects/seamonkey/releases/updates/en-US.rdf
>+update_notifications.provider.0.datasource=http://www.seamonkey-project.org/releases/updates/en-US.rdf
Speaking of update servers, this is the old update system which can go (including its prefs in suite's browser-prefs.js which shouldn't be there).
Attachment #290524 - Flags: superreview?(neil)
Attachment #290524 - Flags: superreview+
Attachment #290524 - Flags: review?(neil)
Attachment #290524 - Flags: review+
Attachment #290528 - Flags: superreview?(neil)
Attachment #290528 - Flags: superreview+
Attachment #290528 - Flags: review?(neil)
Attachment #290528 - Flags: review+
Attachment #290528 - Flags: approval-seamonkey1.1.8? → approval-seamonkey1.1.8+
(In reply to comment #3)
> Speaking of update servers, this is the old update system which can go
> (including its prefs in suite's browser-prefs.js which shouldn't be there).

Checked in on trunk with that change.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
...and also checked branch patch into 1.8 branch.
I just realized we also need to swap splash screens on branch - here's the Windows one.
Attachment #291494 - Flags: superreview?(neil)
Attachment #291494 - Flags: review?(neil)
Attachment #291494 - Flags: approval-seamonkey1.1.8?
...and here's the Linux splash.
Attachment #291495 - Flags: superreview?(neil)
Attachment #291495 - Flags: review?(neil)
Attachment #291495 - Flags: approval-seamonkey1.1.8?
Attachment #291494 - Flags: superreview?(neil)
Attachment #291494 - Flags: superreview+
Attachment #291494 - Flags: review?(neil)
Attachment #291494 - Flags: review+
Comment on attachment 291495 [details]
mozilla/xpfe/bootstrap/splash.xpm (1.8 branch)

Unfortunately I don't have an .xpm viewer...
Attachment #291495 - Flags: superreview?(neil) → superreview+
(In reply to comment #8)
> (From update of attachment 291495 [details])
> Unfortunately I don't have an .xpm viewer...

The .xpm is the same image as the .bmp, just in the other image format.
Attachment #291495 - Flags: review?(neil) → review?(ajschult)
Comment on attachment 291495 [details]
mozilla/xpfe/bootstrap/splash.xpm (1.8 branch)

Forgot to note with the review request - ajschult should be able to view the .xpm, I guess :)
Attachment #291495 - Flags: review?(ajschult) → review+
Attachment #291494 - Flags: approval-seamonkey1.1.8? → approval-seamonkey1.1.8+
Attachment #291495 - Flags: approval-seamonkey1.1.8? → approval-seamonkey1.1.8+
You need to log in before you can comment on or make changes to this bug.