<< Weekly Status Report, W17/2010 | The roads I take... | Integration eines Magento-2-Webshops mit FreeFinance und selbstgebautem Warenmanagement >>
Weekly Status Report, W18/2010
I got 2.0.5 builds going (candidates are up for testing) and pushed them to the beta channel after some testing. Actual release might get delayed due to 3.6.4, with the same security fixes but even a large feature, is being delayed as well.
For that release, I also went through L10n signoffs and after some review could add en-GB and zh-CN (Simplified Chinese) to our shipped locales - thanks to those L10n teams to provide this cool work!
Also, I tried to get things lined up for cutting 2.1 Alpha 1, which took a while because of some blocker bugs needing to get out of the way (build breakage prohibiting Windows test runs, MDN breakage, Modern toolbar menubutton breakage). Meanwhile, into this week, it looks like we finally have what we need for this first Alpha.
To support those releases and get them on track, I created preliminary release notes and filed a number of bugs tracking various stuff that needs to happen for the releases.
We had a very interesting build problem I looked into this week, which happened when the debug builds on Windows wanted to install tests for the content module. The error message of "nsinstall.exe: bad file number" was quite unhelpful, but when I investigated by taking one of our build slaves off the build bool and attacking it manually, I found out we actually seemed to be hitting a length limitation in the command line of the Windows build environment. We had been hitting this on those builds first (and not on other SeaMonkey or even on Firefox builds) as paths in that configuration are slightly longer than elsewhere. Installing 321 test files in one command line could make it grow even over 33,000 characters, and somewhere in that range we did hit a wall (smells so much like 32,767 but we seemed to get somewhat over that - maybe it's just argument string length or such).
In the end, I made a patch for splitting that list of tests into two parts, the patch was accepted into mozilla-central and the problem is gone now.
The places bookmarks patch set has been on the backburner this week, but I followed as de-XBL of toolbars and menus landed for Firefox, will adopt this as soon as I come around to.
- Various Discussions:
Account Manager, Summit, module owners, tree/network issues, etc.
I sent a lot of this week not only recovering from a cold but also at a local FOSS conference called "Linuxwochen" in Vienna. Lots of conversations there were pretty interesting, including those on getting an open geolocation database service going and thinking about organizing open source meetings together with the OpenOffic.org guys - oh, and probably even the one with the Microsoft guy who presented their "surface" desk and who didn't see why I disliked that it wasn't using an open software stack. The FSFE team congratulated me to that discussion the day after...
My talk on "Mozilla is more than Firefox" was quite well-received, people seemed to be particularly interested in mobile, Weave and Labs, and video, and someone also told me that "Mozilla should advertise the philosophy more". Also, the Mozilla swag I did get some time ago is now almost fully in the hands of the people.
Another fruitful conference experience with a lot of interesting chat with cool people - now let's put an interesting first 2.1 alpha into the hands of another set of cool people!
Entry written by KaiRo and posted on May 11th, 2010 21:10 | Tags: L10n, Mozilla, SeaMonkey, Status | 7 comments
from Brussels, Belgium
At some point between the last 2.1a1pre nightly and the first 2.1a2pre, the addons manager has become useless (and all extensions including ChatZilla, DOM Inspector and Debug/QA UI have stopped functioning). I don't know if the 2.1a1 release is affected. See bug 565090 -- Mossop has reacted.
from Brussels, Belgium
P.S. Bug 565090 is a consequence of bug 561600 "Implement the New Addons Manager UI for SeaMonkey (about:addons)", meaning that, until the latter is fixed, no extensions, themes, languages, search engines or even plugins will work in SeaMonkey 2.1a2pre.
I also noticed that Sm 2.1a2pre loads no more that 44 tabs at startup, no matter how many are in the "Home Page" tab group. No bug yet from me on that count (I'm waiting on 2.1a1pre until bug 561600 gets fixed).
So what is DOM 2.0.5 which just auto-downloaded as an add-on to Seamonkey 2.0.4?
And will the shortcut-sharing bug be fixed?(A WinXP desktop shortcut that is supposedly to the /ProgramFiles/Seamonkey2 directory where I have Seamonkey 2 always brings up 1.1.18 (in a separate directory) first on startup,then Seamonkey 2 after 1.1.18 is exited and Quicklaunch prompted to exit Seamonkey...is there no Quicklaunch in Seamonkey 2?)
[when did your comment form go all-German?]
DOM Inspector is a built-in add-on in SeaMonkey, and yes, that add-on just did release a new version.
No idea what the shortcut thing is, I'm not a support person. But no, "Quickluanch" does not exist for SeaMonkey 2 - and we don't really support any configuration for users that have multiple versions installed. It's surely possible to do that, but make sure you know what you are doing, we take no gurantees your computer magically knows what version should do what.
And my comment form is always German when your browser is set to prefer German.
from the US
I'm just hoping 2.1 doesn't take away the feature in 2.0.x, where the browser crashes every few hours. It's great, because it really shows the capabilities of session restore.
Eh, my browser is set up to prefer Esperanto (just because it's awesome), but I do have German in the list too, because I'm currently studying it.
Keith, unfortunately, we are working a lot on removing different of those "crash" features, and given that this seems to be one of the more prominent and useful features of Flash, the work on being able to run it in a separate process will likely cost us a good number of those crashes as well, reducing those session restore showcases.
Also, if you have set German to being preferred by your browser over English, this blog should try to show you stuff in German (it's the only two languages it supports, as they're the only ones I really know well enough).