Just want to make a quick post (which I should’ve done about four hours ago but got sidetracked) to mention that SeaMonkey 2.53.3b1 is released!
Please do check out this new release. Why? “Coz the Rock says so.” (some obscure 90’s WWE quote).
Incidentally, the automation is still being worked on; which means that the builds were generated by IanN and frg. That said, I am closer to getting something running. At least the automation builds *are* green. Now it’s the process of releasing…
Just would like to announce that SeaMonkey 2.53.2 has been released.
Thanks to the SeaMonkey dev team for their hard work!
NB: Still practicing on making announcements.. this one might be a bit short.. somewhat overloaded a bit right now.
I’ve taken some time to try to fix the update situation and have come across a clash between the old update (for lack of a better word) necessities to the new update necessities.
In the past, we had partial and complete mar files in the release’s update paths without checksums and these mar files are served by Mozilla’s bouncer (somewhat like a load-balancer or somesuch thing which I never really understood). The checksums were provided in the snippet directory when the updates were generated in the forms of ‘complete.txt’ and ‘partial.txt’.
I’ve tested out our update server with one version. 2.29. The client *can* grab the update to 2.53.1 *but* it can’t update to it. (Restart produces the dialog that the update couldn’t be applied). I didn’t check why it didn’t work; but I suspect that the update format for 2.53.1 isn’t ‘compatible’ to 2.29’s update code.
So all in all, the update backend and process is a complete mess. While I can dedicate some time to figuring out this mess (I can’t right now, as I’m in the process of getting 2.53.2 uploaded), I will take some time before the backend can get to the point of ‘working’; though I suspect it’s going to be at a cost of not supporting versions (i.e. 1.x or 2.0.x and possibly others).
It is a mess… *sigh*
Another notification of another one of my goofups.
This time, this pertains to the paths mentioned in the checksum files. To my chagrin and dismay (chagray?), the file paths mentioned in those checksums are wrong. I haven’t checked them all; but, I believe all of them have the following format “tmp/releases/2.53.1/…” when they should just be without that prefix.
The reason for this wrongness is that I had used a temporary path to generate the structure of the whole release tree. I had forgotten that I had done that when I moved the release tree to where it should be, i.e. releases/2.53.1.
I am in the process of replacing all those files with the proper path; but, it’s going to be a tedious one. In the meantime, please be aware of that issue if you do check for the checksums.
Just wanna drop a quick note stating that SeaMonkey 2.53.2b1 has been released.
I apologize (again… ) for the delay. Between technical issues and personal issues, it took me some time to get things done. But, well… c’est la vie. So, no pithy or humorous notes.
The project has officially released SeaMonkey 2.53.1!
This time, it only took me a week to get my smeg together! Improvements galore to the releasing process, so the next time, it should be even faster (touch wood).
Kudos to frg and IanN who made the builds. Yes, they’re my automation! Hahahh… *sigh*. Seriously, I am working on getting the automation up. Really!
Let’s chortle in our joy!
Yes, 2.53.1b1 is finally out!
No pithy comments this time.
Thanks to all involved! [*You* know who you are… *wink*]
On behalf of the SeaMonkey project, I’d like to wish everyone a very Happy, safe, prosperous and healthy New Year!
First and foremost, 2.53.1b1 will soon be released; pending final checks. Once that’s done; it’s good as going gold. That said, I did miss a few items (updating the checks… *sigh*); but it’s not going to be a biggy. (The crashreporter files for all platforms except Win* were missing.)
Next, I just want to take this opportunity to mention that the delay in the release was not frg’s or Ian’s or anyone else’s fault but mine. I take the full blame for the delay in the release as I was trying to streamline the release scripts, which took the brunt of the time. So please, I appreciate that if anyone has any complaints, please direct your ire and frustration at me, not them. They’ve done a HUGE amount of work doing the builds, something which was supposed to be my doing. So they deserve all the kudos and gratitudes for getting things done.
I’m hoping that before the next release, I’ll at least get some semblance of the builds and updates working so that they don’t need to bother with the builds and concentrate on getting the fixes in.
So I need to apologize to everyone for the delay. While fixing the infrastructure has been a very long and arduous project that *still* hasn’t come to any fruition yet. I’m not making any excuses for my tardiness (despite being in a job and a family to feed…), I take this responsibility seriously.
In any event, thank you everyone for your patience with the project and with me.
Actually, not really. We’ve kinda moved away, though we still have a presence and there’s nothing to sell…
If it wasn’t official then, it’s official now. Mozilla has decided to switch off irc.mozilla.org in March 2020. In its place, they’re going to use Riot/Matrix.
I just want to take this opportunity to thank all those hardworking sysops/ircops at irc.mozilla.org for the plethora of years of protecting the irc servers from undesirables [I do have a much better set of language, but this is a public, family friendly blog…soooo… use your imagination. 😛 ].
That said, just want to make sure everyone that still supports SeaMonkey to mosey on to Freenode’s #seamonkey channel.
Thanks irc.mozilla.org! As they say, irc.mozilla.org is dead… or dying.. Long Live irc.mozilla.org! [kinda reminiscent of SCL3 is dead! Long live SCL3!]
PS: And yes.. we’re still around.
SeaMonkey is currently as far behind the release schedule (rapid release or otherwise). Mozilla isn’t making it easier for us to release things; but, hopefully we’ll be under our own release schedule (if we’re not already) for Mozilla to have any affect on us.
That said, I can’t help but feel that I’ve dropped the proverbial ball on this release. I’d like to personally offer my own apologies for the delay. It’s entirely and wholy my fault and not the fault of the other devs. I have a lot of ideas to get things working again; but, I’m hoping I’ll get the chance to do what I’ve set out to do for SeaMonkey.