![]() It doesn’t give me pleasure to state it outright but it’s always the resources issue. I do apologize for the long windedness and the decision to only update 2.53.x. SeaMonkey 2.49.2 contains (among other changes) the following major changes relative to SeaMonkey 2.49.1: SeaMonkey 2.49. So the final conclusion, as mentioned above, is that only 2.53.x + will get updates. As mentioned earlier in a post on the support mailing list, only versions > 2.33 (iirc) can be updated due to certificates not being recognized and that can’t be helped.)) (Still, a part of me is reserving the right to modify the system to allow updates from 2.49.x to 2.49.5 at least. All other versions polling for updates will not get any. The benefit of the SeaMonkey project sticking with only 2.53.x + updates is that these updates will work on systems being updated. I realize this may sound like an excuse for ignoring old software but there really only so much we can do particularly when the engine is changing so rapidly that we’re trying to keep track of the *latest* stuff coming out from Mozilla. It’s just that using it on an actual system could potentially harm the system. Does this mean the old versions can’t be used? No. This is the unfortunate by-product of technological progression. Is it possible to set up a VM to build old software? Possibly but is it worth the time and resources? Unfortunately, the answer here is no. Furthermore, even websites are now finicky as to which browser can view them, which further adds to the frustrations of using old SeaMonkey versions. If big corporations can’t/won’t support old operating systems what hope do we (as a small group of volunteers) have? Is this a justification to leave old software high and dry? No but it is not realistic to expect a small group of volunteers to support software that no longer build on any system. Ditto with the Windows Servers (NT, to 2008). Win 1 to (recently) Win7 are no longer supported. The 2.49.1 – 2.49.4 to 2.49.5 update is a special case as the 2.49.5 update files had changed and we missed the opportunity to create a set of transitional update files for that.īig corporations, like Microsoft, no longer support old operating systems. As of this writing, I’m not entirely sure the 2.49.* family will ever be updated (but you’ll never know). Any other previous versions are no longer supported in terms of updates. The SeaMonkey Project will only be supporting the 2.53.* (Gecko 56) family. I had posted this concern on the lists and probably here as well but I’m just going to repeat myself. ![]() *That* was my intention.Īs in with intentions mixed in with life, things aren’t that simple. Like, if you had installed 1.x, you’d be able to upgrade to 2.53.7.1. My original intention was to allow any version upgrade to any other greater version (barring operating system restrictions etc.). Tl dr: SeaMonkey 2.53.* (and newer) are the only versions that will have updates. ![]() will be left as is (mainly because one of these days, that domain will be decomissioned (since it is Mozilla’s)) I’m hoping to switch the to using the new update system. It’s also based on customised versions of the Mozilla applications - you’ll find a web browser, an email client, IRC chat client and a web editor for producing your own homepage.I’m putting this post up to better clarify the situation with the updates. 2.57 will be build from a new 2.57 gitlab repo based on the comm-esr60 repo. Because of not enough developers this is a slow go and we will distribute interim 2.53 versions. SeaMonkey 2.57 is being developed together with 2.53 and then released as soon as possible. It’s not a new suite of Internet software, as it’s been around for a few years. SeaMonkey 2.57 originally based on Gecko 60 in comm-esr60. Mozilla have achieved this with their SeaMonkey suite. For this reason, anyone who can produce a fully-integrated all-in-one Internet suite, is on to a winner. However, with some many choices, options and solutions, it’s easy for these tools to interact poorly. More recently things have changed somewhat and users have realised that third-party developers can design and produce software that enhances their browsing experience. Internet suites became somewhat redundant and the Internet was dominated by one browser and one key developer. One particular suite, Turnpike, was sold to Demon Internet, for millions of pounds, before Microsoft started to take the Internet more seriously (read: build apps into the operating system).Īfter this, users could install Windows and find Internet Explorer, basic email and a dialup client that enabled them to connect to their ISP with few issues. Indeed, I ran a business based around producing a suite of software that got users on to the net with ease. Back in the late 90s, the rage was to make Internet software as easy to use as possible.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |