After 6 builds (tries), we are still mired in the morass that is l10n repacks.
For those who are curious, it’s bug 1231349 .
There is a workaround for this; but, it is considered a hack and not really solving the problem, which afaik, is basically the backend mozilla code having some repacking difficulties with the extensions that we include (DOMi, Chatzilla). While we figure out the backend code, I’m spinning up a DE repack to test out the workaround and to determine if there are issues with releasing repacks created from the workaround.
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).
Yes! SeaMonkey 2.40 is out.
(Since it is getting late, I'm copying and pasting what I wrote in the newsgroup post. I apologize for not taking the time to make a decent post, but it is past my bed time. :P )
After so long a delay, for which we apologize, the SeaMonkey
Project is pleased to announce the release of SeaMonkey 2.40!
So please check out  or .
Please note that the website information, while updated for
2.40, still requires a bit more work.
We cannot repeat this enough. Thank you everyone for your
patience with us. This very long delay due to infrastructure
and resource issues has been very trying on a lot of people.
It has been a very tough release. I think it's the
toughest one I've done. However, this isn't to say that
I did this alone. Kudos go to a lot of people, particularly
the guys/gals in Mozilla's IT and RelEng dept.
I particularly want to thank Nick Thomas for his sheer
brilliant idea that helped me unhork the partial mar upload
script as well as pointing out the necessary changes
to migrate off FTP to S3.
Thanks to Jens Hatlak for taking the time to do the Website
patch. (Really, sorry for the delay.)
Also, thanks to Justin Wood for giving me this opportunity
to work out the problems myself. If you all take a look
at bug 1233615, I think I rivaled the mess I did with
the GTK bug (conveniently forgotten the # :P ). The
repo changes I made... oh boy. Only time will heal
the mess^H^H^H^H wounds. ;P
Anyway, most of all, thanks to all the users out there
for hanging on to this project. The words of encouragement
(especially during the broken-hand period) definitely gave
me a boost of energy.
Oh. Before I forget and in the light of being transparent,
there is a chance I might have goofed something up, especially
during the 2.39 Win32 builds as well as the 2.40 builds and
also the partial mar and complete mar updates. I hope I
didn't screw things up too much, if at all (here's hoping).
Please do post here on your findings.
Anyway, thanks again.
 - http://www.seamonkey-project.org/releases/2.40
 - http://www.seamonkey-project.org/releases/seamonkey2.40/
PS: I think I'll post something later, when I have most of my mental faculties with me. :P
Adrian Kalla again contributes unofficial localized installers and language packs in various languages for WINDOWS and Linux: Trunk & Beta & Aurora & Release .
Only for testing, you will use those builds on your own risk. I recommend to create a backup of your user profile before you start testing those builds.
The SeaMonkey-Project is living thanks to contributions of the community, by “manpower” or by financial support. Any contribution, also small amounts by Flattrs, are appreciated. You can donate via the SeaMonkey e. V. donation page or via the private donation initiative I started few days ago. The reasons why I started my private Donation campaign and why I currently can’t recommend donations to the SeaMonkey e. V. you can find here. You will reach my private SeaMonkey Donation Page (not initiated by or under responsibility of SeaMonkey or mozilla) with a click here or on the image at the right.
Posted in General, News, seamonkey, Uncategorized
Tagged Flattr, need help, News, Nightly, PayPal, please test, QA, release, seamonkey
Despite all big problems, we have a first unofficial 2.44a1 SeaMonkey Build – even localized with several languages 🙂
Posted in News, seamonkey
Tagged 2.44, Bugzilla, coffee mug, competition, confirmation, improve, need help, Nightly, please test, QA, reward
The first part is complete.
The second part is where it gets hairy. The move to S3 has completely broken the second part of the release process and so our scripts will need to be retinkered.
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!
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.