Closed Bug 759315 Opened 8 years ago Closed 8 years ago
Add a page to the Sea
Monkey website about the latest releases available for Legacy Platforms (e .g . PPC)
From: SeaMonkey/StatusMeetings/2012-05-29 -> 2.x (Last, Current, Next) <https://wiki.mozilla.org/SeaMonkey/StatusMeetings/2012-05-29#2.x_.28Last.2C_Current.2C_Next.29> * SeaMonkey 2.6.1 for PowerPC/G4 on Mac OS 10.5.x is available. IanN says we should advertise that more (and other contributed builds). * The current plan is to create a new page for latest builds available for "Legacy Platforms" e.g. PPC containing links to 2.6.1 PowerPC/G4 and also perhaps to TenFourFox and TenFourBird. We can then link to that from our main release page.  http://code.google.com/p/seamonkey-ppc/downloads/list  http://www.floodgap.com/software/tenfourfox/  http://en.sourceforge.jp/projects/tenfourbird/
Also, SM 2.10 will drop support for Win2k, and WinXP without SP3.
Component: Project Organization → www.seamonkey-project.org
Product: SeaMonkey → Websites
QA Contact: organization → www-seamonkey-project-org
I hope that if this is done, it will come with a big scary warning about the insecurity of both those old platforms and those old builds.
I think TenFourFox is backporting security fixes even to their ESR release.
(In reply to Robert Kaiser (:firstname.lastname@example.org) from comment #2) > I hope that if this is done, it will come with a big scary warning about the > insecurity of both those old platforms and those old builds. Absolutely. At least as far as our own builds are concerned, that is. For external sources we should indicate that we cannot assess their security, given that even if a build provided by an external source is secure at the time of one of us checking it, that may change any time. People need to check the original location and make up their mind themselves.
(In reply to Philip Chee from comment #3) > I think TenFourFox is backporting security fixes even to their ESR release. We're just mirroring esr10 and adding our own patches on top of it. The plan is to switch to 17 as soon as it is available and jump ESR-to-ESR. For the adventurous, builds based on mozilla-release are also available in the unstable channel to keep the port viable (13 will come out shortly). The person working on seamonkey-ppc (note: not affiliated; nor is tenfourbird) has publicly stated he intends to build more recent versions and I imagine the sticking point was bug 691898, which was finally fixed recently.
http://code.google.com/p/seamonkey-ppc/ http://code.google.com/p/seamonkey-ppc/downloads/list I see that SeaMonkey 2.10 for Mac OS X 10.5.8 PowerPC is available from his website.
WIP: http://stage.seamonkey-project.org/releases/legacy Goals: * Strong disclaimers * Zero maintenance: Do not list versions, state security status or up-to-dateness of third-party builds * Do not link old versions, since we don't officially support them [debatable] [If anyone needs the staging website credentials, kindly send me an email.]
Assignee: nobody → jh
Status: NEW → ASSIGNED
[Bugzilla says Stefan is away until mid-August.] Ian and Ratty, can you please check the page from comment 7 and give me some feedback? I'm mostly interested in whether I got the facts right, whether anything important is missing and if there are any language issues. We can improve the page later if need be, but I want to get this initial version off my back ASAP (it'll get mentioned on the status meetings every time until it's fixed).
> (cf. System Requirements) See our system requirements > In other words, we do not support any of the applications and versions listed below. Drop the "In other words" Although we do not support some legacy platforms, other projects provide builds that are based on the same platform as SeaMonkey, Firefox and Thunderbird. The SeaMonkey Project is not associated in any way with these projects. We cannot provide support or help for these. We cannot verify their security or stability. You should make your own judgement as to the suitability of any of these third party builds you intend to use.
(In reply to Philip Chee from comment #9) > Although we do not support some legacy platforms, other projects provide > builds that are based on the same platform as SeaMonkey, Firefox and > Thunderbird. I modified that sentence a bit since I didn't like the "not support some" part (which, to be fair, I had introduced). Now it reads: "There are some legacy platforms that we do not support anymore but for which other projects provide builds that are based on the same platform as SeaMonkey, Firefox and Thunderbird." A bit long-ish, but at least the part I had trouble with is now better IMO. Otherwise I merged in your suggestions (thanks!); only re-added the emphasis (using the strong tag).
IanN: ping for feedback
(In reply to Jens Hatlak (:InvisibleSmiley) from comment #11) > IanN: ping for feedback I wish there was a way of requesting feedback without a patch for this component.
> There are some legacy platforms that we do not support anymore but for which other projects > provide builds that are based on the same platform as SeaMonkey, Firefox and Thunderbird. Do we really mean platform here or is something source code better? > Please note however that the SeaMonkey Project is not associated in any way with these > projects. We cannot provide support or help for these. We cannot verify their security or > stability. You should make your own judgement as to the suitability of any of these third > party builds you intend to use. Would it be better to have this as a new paragraph, maybe even with a heading of "Note" and the first sentence tweaked slightly?
(In reply to Ian Neal from comment #13) > Do we really mean platform here or is something source code better? "share the same code base"? > Would it be better to have this as a new paragraph, maybe even with a > heading of "Note" and the first sentence tweaked slightly? Breaking up long paragraphs is hardly ever wrong. ;-) I did however drop the heading idea; it looked a bit strange to me (headings below "Third-Party Projects" should IMHO only refer to individual projects). Staging website updated accordingly, waiting for feedback.
While integrating this into the main releases page I found that most of the headings should actually go under the heading of the latest release. This then allowed me to cleanly extend the hierarchy with a new heading and to stop linking to a non-heading from the bullet list. The new section's text is included in the patch as well, but you can read it on the live page in a couple of minutes anyway. ;-) Checking in src/releases/index.en.html; /www/seamonkeyproject-org/src/releases/index.en.html,v <-- index.en.html new revision: 1.250; previous revision: 1.249 done RCS file: /www/seamonkeyproject-org/src/releases/legacy.en.html,v done Checking in src/releases/legacy.en.html; /www/seamonkeyproject-org/src/releases/legacy.en.html,v <-- legacy.en.html initial revision: 1.1 done
I'll mark this fixed but if any of you feel the new text needs further tweaks, please feel free to leave a comment and continue the discussion.
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Where should SeaMonkey-PPC bugs be reported? Please see: https://bugzilla.mozilla.org/show_bug.cgi?id=338041#c21
You need to log in before you can comment on or make changes to this bug.