2.40 news

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!


About ewong

I'm a SeaMonkey dev/RelEnger and a bit of a buildbot dev.
This entry was posted in seamonkey. Bookmark the permalink.

6 Responses to 2.40 news

  1. Albert says:

    No problem. Your work is great with this Suite , thanks

  2. Martin says:

    I’m eagerly waiting for the new (localized) build, thanks for your efforts!

  3. While the paint dries on 2.40 release, any news of 2.44a1 trunk? (Firefox 2.47a1 is out, but SeaMonkey seems stalled since 9 January).

    • ewong says:

      iirc, trunk (and aurora now) is busted because of bug 1238428 and apparently another bug (haven’t filed it but I’m guessing TB’s also affected as it’s in mailnews/)

  4. dilworks says:

    No problem, I’m a very patient guy…

    Speaking of things I should wait for: Mozilla is now shipping Win64 builds of Firefox. Is there any hope for official (or at least contrib) Win64 builds for Seamonkey? I really REALLY wanto to get rid of 32-bit legacy on my Windows boxes… just like I did under Linux 10 years ago.

  5. George says:

    Thanks for all the developer’s work on SeaMonkey. I try to donate every once and a while. I appreciate the blog and the updates. In a way, I am glad SeaMonkey’s updates are more spread out. It seems like everyday there is a new Chrome or Firefox version out. Still love SeaMonkey! Thanks Again!

Leave a Reply

Your email address will not be published. Required fields are marked *