SeaMonkey Project Blog

Hi All,

I have an update on the updates for the updates…

The DNS has been migrated over to the new server.  The old servers will be going soon…

Anyway, I’ve been looking at the logs and notice that some of the requests are working while those that should work aren’t, so, the rules need a bit of tweaking..  Yes, there is an elephant in the room.  Am I testing in production?  No, not really.  I have a staging area.  It’s just that I can’t manage two separate update servers and I certainly would’ve gotten confused and updated the wrong one.   So I moved the code to the new server (but had to update it a bit, again.. the confusion part) and have setup the staging and production trees.  However, as Jenkins can’t touch this infra, it’ll have to be manual for now.

Another era is about to come to an end…  The Azure era…  *sigh*  But as Opus once sang…  “Life is Life!”  (tautologically correct…  akin to 1 is 1…  but I digress).

Best regards,

:ewong

Hi All,

The updates aren’t working, which isn’t a surprise…  well, it is actually.

It’s mostly a PEBCAK with error number ID – 10- T.

We’re moving updates server to a different server on a different cluster (note: I’ve been wanting to say this, even if we’re just moving to a different provider… so cluster=provider).  So it should be so easy, right?  Move the archive (done), and move the code(also done), then it should just be $$ profit.

So, while the current update system is up,  I’m going to request a change in the DNS such that it points to the new server and start working on fixing the different update criteria to actually get things working again.

I do apologize for the delay.  I’m now wondering if lion-taming is a hot job?

:ewong

Hi All,

First of all,  on behalf of the SeaMonkey Project, I would like to wish everyone a very Happy, Prosperous and Healthy New Year!

To start things off, the SeaMonkey Project is pleased to release a security update to SeaMonkey 2.53.22 due to some security fixes.

Please check out [1] and/or [2].

:ewong

[1] – https://www.seamonkey-project.org/releases/seamonkey2.53.23

[2] – https://www.seamonkey-project.org/releases/2.53.23

Hi All,

The SeaMonkey Project is pleased to announce the release of version 2.53.22.

As mentioned before, the binaries are x86-64 only.

Please check out [1] and/or [2] for further details.

:ewong

PS: Actually, the release was done last week (iirc) and was hoping to do the blog and updates over the weekend (specifically Sunday); but had to head out of town.  Lost my train of thought and missed posting.  Ian’s email jogged my brainfog and here’s the post and the updates.

[1] – https://www.seamonkey-project.org/releases/seamonkey2.53.22

[2] – https://www.seamonkey-project.org/releases/2.53.22

Hi All,

The SeaMonkey Project is pleased to announce the immediate release of SeaMonkey 2.53.22 Beta 1.

Please checkout [1] and/or [2].

Please also note, just to be explicit,  SeaMonkey 2.53.22 Beta 1 dropped support for the x86 binaries (Linux i686 and Win32).  So 2.53.21 is the last SeaMonkey version to support Linux i686 and Win32.    I actually use both Linux i686 and Win32 binaries, so I’m kinda sad to see them go.  Anyone remember the OSX x86 binaries (I think it was called Universal binary).  ?    C’est la vie, I guess.   In one way, this lessens the burden of the devs.

Now it’s all x86_64, baby!   x86 binaries have died.  Long live x86 binaries!

:ewong

[1] – https://www.seamonkey-project.org/releases/seamonkey2.53.22

[2] – https://www.seamonkey-project.org/releases/2.53.22b1

Hi All,

The SeaMonkey Project is pleased to announce the immediate release of SeaMonkey 2.53.21.   There are a few security updates and …

*What?  Um.. No,  I didn’t see it.  I did look at the website patch…  Yes, it’s the same as reading the release notes.  It clearly states that it’s a point release and it’s a security patch…   Anyway…. *

Please check out [1] and/or…

*What now?  Look, I’ve been doing and/or for some time…   What do you mean exclusive or?  Ok.. this time, you make sense.*

Please do check out [1] and [2].

:ewong

PS: Did I mention the Updates will be forthcoming…?   Yes, the updates will be forthcoming…if it hasn’t already been done already when you read this.

PPS: Yes, trying to jazz things up…  think of this post being Rik Mayall’d.  (RIP).  The People’s Poet…

[1] – https://www.seamonkey-project.org/releases/seamonkey2.53.21

[2] – https://www.seamonkey-project.org/releases/2.53.21

Hi All,

The SeaMonkey Project is pleased to announce the immediate release of SeaMonkey 2.53.21 Beta 1.

Please check out [1] and/or [2].

As usual, updates are forthcoming.

:ewong

[1] – https://www.seamonkey-project.org/releases/seamonkey2.53.21

[2] – https://www.seamonkey-project.org/releases/2.53.21b1

Hi all,

As subjected, we’re migrating to a new Update server over the weekend (possibly even sooner)and while I have tested it a bit, nothing beats testing in production.  ;P

Seriously, though,  there’ll probably a bit of a hiccup (I have water), but shouldn’t be so terrible that we need to resort to returning to the old server.

Best regards,

:ewong

Dear All,

It is with very heavy hearts that we, at the SeaMonkey Project, announce the sudden passing of one of our core dev and releng, Bill Gianopoulos (aka WG9s) on the 6th January 2025.   Here is his obiturary (https://www.chesmorefuneralhome.com/obituaries/william-andrew-gianopoulos/20284/)

I wish there was something to say… but.. still stunned by this news.

R.I.P.  Bill!

:ewong