Monthly Archives: September 2018


SeaMonkey’s infrastructure has officially been decommissioned.

May the memory of all these years of building SeaMonkey on these systems remain in the annals of SeaMonkey’s history and in all of the current and past contributors who had the fortune of administrating them (and fighting against their impulsive bustages).  An era has ended.

(Lights a candle for each of the following systems: )

  • sea-hp-linux64-{2,13}
  • sea-vm-linux32-{2,7}
  • sea-mini-osx64-{1,4}
  • sea-vm-win32-{1,4}
  • sea-win32-{01,04}
  • sea-master1
  • sea-puppet
  • the Windows loaner

A new era has begin.

Thank you for all the contributors and users who’ve supported this project and continue to do so despite the changes and the delays in releases.  We appreciate your continual support and patience as we get the new infrastructure up to par.


SeaMonkey Release Engineer

Last day…

Well…  all this preparation and migration has culminated to this final day after which our dear ol’ infrastructure will be gone forever.

It’s like saying goodbye to a friend…

For Auld Lang Syne… my dear… for Auld Lang Syne… We’ll drink a cup of kindness yet… for Auld Lang Syne…

I remember fondly of accessing the systems through the jump host…

“Parting is such sweet sorrow…  ”


SeaMonkey Project’s own Lamenter.

Website is… up…. down…up… what?


Some, if not all, of you may have wondered what the smeg was going on with the website.  It’s up.  Then errors out.  Up.. Errors out.

The reason is simple.

PEBCAK^H^H^H^H^H^H Teething errors with the website… yeah…

Seriously, sorry about the missing website.  It should stick now.

On my defense, I had to reverse-engineer the behaviour of the old website as I had no access to it.  This includes ‘how’ the website is setup, and how it’s built and the cronjobs necessary.  So I should’ve expected some teething errors.


SeaMonkey Project’s own befuddler.

End of an era…

Dear All,

It is an end of an era as today is the last day of SeaMonkey’s old infrastructure.   Come 12th September, it’ll be shut down for good.  We’ve been using this infrastructure for more than ten years and it’s sad to see it go; but c’est la vie.

Now it’s fully on the SeaMonkey’s team to get the new infrastructure working and running.  What does this mean to everyone involved?  It means more involvement in getting things working, which unfortunately, isn’t the case right now.   The new infra is still going through the fixing part.

What this means is that any future releases will be delayed until this infrastructure is behaving properly.

I’d like to take this opportunity to thank Mozilla for all these years of helping us maintaining the infra as well as our multitudes of requests for items/bug fixes, etc.

I also would like to thank the users for your patience and understanding.

Best Regards