SeaMonkey Project Blog

Yes.  Long time no post.

Why? Is the SeaMonkey project dead? The last was 2.40!  That’s a long time ago! (well, not really…  but long enough.)  Where is everyone?  Why has there been no posts or mentions? (and a host of other questions…)

Just want to mention that 2.46 is currently being spun… and by spun, I mean wrenched…  like loosening a very tight bolt that’s been superglued to the screw.

“What do you mean?”  some might ask.

At the start of the process, we managed to hit a few hiccups… well…not so much as hiccups but boulders the size of Boulder, Colorado with large signs saying “Stop… you cannot pass!”  (Hyperbole much?)

tl;dr (or if you wish, you can still read)

Since 2.40…  the releng team has been ‘trying’ to unbust the infrastructure to the point that things are starting to go green. (Yay!)  though we still have some l10n nightly troubles (bah humbug).   So with the desperate need of getting a release done, the project felt it was a good time to build 2.46 before something crawled out of the moco workshop to put a kaibosh on our release…  little did we know.

So, we (not really throwing caution to the wind… more like hoping with baited breath) started the build….

… only to come to a crashing halt at the 2nd step. (Moco *did* make a change to hg.mo’s infra (thus changing the fingerprint) and caused the build bustage as well as some environment variables  that should’ve been set but weren’t for some reasons (probably changes in the releng code that didn’t get translated to the release releng code…  my bad).

So.  2.46 will be out.  Just not today and my guess, not tomorrow either.  Sorry.   But since everyone’s waited for so long…  what’s a couple of days more? You’re right. Not a good excuse.

Please do stay tune to this channel… more updates soon as we unhork those boulders (hyperbole.. I know).

:ewong

Well…while this isn’t super good news since 2.40 still isn’t ready (Win32 candidate builds are up though but haven’t been ‘processed’ yet), we are progressing slowly.

The issue now lies with l10n.  (*roar* indeed ;P)

I was hoping that I’d fire off the l10n repacks automatically; but, something during the repack is causing the loaner to bsod (according to the windows recovery dialog).  So, I am watch the whole process go. (Think of watching paint dry, minus the paint fumes).

Once this is done, it only signifies the end of the first half.  The second half will be ‘interesting’ (for some loose definition).

So we  very much appreciate everyone’s extreme patience with us.  You guys/gals are the best!

:ewong

Up until now, I thought 2.35 was a painful spin….

2.40 is completely crazy! Between working on it with a fractured hand(right hand), and all the problems jumping out at every corner, I’m still wondering (albeit softly to myself) whether 2.40 will be released with my sanity intact.

Now,  I do confess I bungled up on the first three builds. Can’t fault anyone on that.  Forgot to change the relbranch on two instances.

So we’re up to build 4. (Personal record, btw.)

Building wise, things are ‘ok’.  Linux* built ok.  OSX64 built ok but failed on the crash-symbols upload. (Fixed the issue. Just retriggered.) WinNT is building (but I worry, since I’m building on a new loaner — the previous loaner was decommissioned without any notice, so I lost  some work there as well as losing track of what needed to be done.)

But the l10n part failed. So we’re figuring that out.

Sorry for the delay. Being out of commission for a few weeks has set my whole scheme out of wack.

:ewong