Not Monday, nor Tuesday..

Hi all,

Just want to apologize for the delay.  Moco RelEngers have been super busy so the bouncer has to be done when one of them are available to update it.

Hopefully soon.   Sorry.  No specific dates, times, or centuries… After the past two attempts, I won’t be that stupid to raise everyone’s hopes up.

:ewong

Monday…definitely Monday…

No, wait.  Tuesday..

Seriously speaking though (or writing, as is this case), the update verifications are done and now, I’m just waiting for the resolution of the bouncer before I can continue.  In hindsight, I should’ve filed that bouncer bug before.  My bad.

So, I am hoping Monday (Pacific time zone) the earliest is when 2.49.2 will be out… latest Tuesday.

Thank you for your continual patience and support for SeaMonkey.

:ewong

welp…

Kinda thought it was toooo smooth.  The updates generation/checking portion of the release process totally hit an obstacle.  A code change in the updater program (something I totally missed, though am stumped as to why we didn’t encounter this for 2.49.1) screwed up the scripts.  I’ve fixed it and have retriggered the update verifications.  Unfortunately, windows’ verification is still busted.

So…  release will be delayed until Sat/Sun or perhaps earlier.

Note to self: Don’t talk about release eta until after that final verification step.  Otherwise, Murphy *will* find a way to put a kibosh on things.

:ewong

Murphy is a very very bad person…

Hi.  ’tis me again.

Just going to say that the updates step failed and after struggling with it for the past day or two,  the release *should* be back on track, plus or minus a day.

:ewong

 

 

Quick update…

I did say I was going to update everyone on the progress.

All platform builds (win32, osx64, linux32 and contrib linux64) are complete.  Repacks are done for Linux32 and OSX64.  Currently doing the Win32 repacks.

I believe the ETA (*emphasis on the E*) should be around Thursday/Friday, provided there are no surprises (update process failing, update verification problems,  etc..).

:ewong

Next release is 2.49.2…and..

I just (after a false start) triggered the builds for SeaMonkey 2.49.2.

Theoretically speaking, there shouldn’t be any issues (touch wood) as it’s pretty much an update to the code for 2.49.1.  and with no major infra changes required, it *should* be ok (did I mention touch wood?).

Will keep everyone updated as soon as I get some feedback from the builders.

:ewong

Download links are ok now

Hi Everyone,

Yes… I goofed up and what I had thought was uploaded wasn’t.

The download links are now working.

Sorry for my bad.

:ewong

404 error

Please note…  getting a 404 error when trying to download from the release links?

Working on this issue right now.  sorry for the mess.

:ewong

2.49.1 is out

Hi all,

After struggling and fixing and struggling more, the SeaMonkey project team wishes to announce that SeaMonkey 2.49.1 is finally out!

Now… it’s fixing the infrastructure, l10n and testing..and updates…

:ewong

Re: Future releases

The changes coming out of the m-c woodwork is a tad bit ‘difficult’ to keep up with, especially with the <sarcasm> huge amount of resources that we have at our disposal.

That said, future releases will be delayed (*sigh*  I mean even *more* delayed) until we get rid of all these monkeys off our collective backs.  Monkeys?  I meant (insert your disliked animal/insect/whatever).  Do note we will release security fixes, should they be required.

The list of required action items:

  1. Infrastructure migration
  2. Aus2->balrog migration
  3. Testing infrastructure fixes
  4. L10n fixes/revamp
  5. Clean up code
  6. Understand where we stand with respect to what’s coming out of the m-c woodwork and how SeaMonkey should ‘evolve’. (I have no answer here tbh.)

This list is tentative as I’m probably missing a few items.   While there are ‘only’ 6 items, the amount of work for each of these items is very involved so they require time and effort amongst the already hectic schedule we run on a daily basis.

As an addendum to this, I appreciate the work that fellow SeaMonkey contributor frg, and the guys at #maildev to keep c-c building.  Without them, SeaMonkey’s future would certainly not be too positive (i.e. biting the dust).  So kudos to their hardwork and effort.

As a contributor to the project, I would like to thank our users for their patience with us and I hope you guys/gals stay with us as we move forward in our quest to dominate the world! (*muahahahaha*)

(*sigh*  yeah … feeble humor… sorry)

:ewong