<< Weekly Status Report, W17/2011 | The roads I take... | Integration eines Magento-2-Webshops mit FreeFinance und selbstgebautem Warenmanagement >>
Weekly Status Report, W18/2011
- Mozilla work / crash-stats:
More looking into fast-rising crashes - nicely, one high-ranking post-FF4 crash has been fixed on Nightly and Aurora now.
Creating a presentation on "CSI:Mozilla" for the Linuxwochen Wien conference - I more and more tend to making "Crash Scene Investigator - CSI:Mozilla" my job title.
Got my MoCo LDAP account running, still working on getting up to speed on everything.
- SeaMonkey Build System:
Did some reviews on the way to 2.1 final.
- SeaMonkey Search:
Landed my patch for linking Engine Manager in sidebar and prefs in time for 2.1 final, split off the hairy edge case as a separate bug.
- SeaMonkey L10n:
Looked through the sign-offs for 2.1 and accepted those that were ready, worked with Callek to sort out the problematic ones.
- Various Discussions/Topics:
Socorro throttling by channel, hyphenation landing and dictionaries, user notification project, 5.0b1, L10n for non-Firefox-desktop apps going onto the train model, Linux gcc 4.5 + PGO problems or not, MeeGo N900 DE testing, etc.
A lot of time this week went into me being at the largest annual local conference on Free and Open Source Software, Linuxwochen Wien. I talked to a lot of people about Mozilla and Firefox, our plans, my work, etc. - and did a presentation that included feature overviews of Firefox 4, 5 and 6 (as far as we know things right now), large projects in work for 7 and later, the new release process, and what we're doing in crash investigation. I hope I could do a bit to improve publicity for us there.
In other news, Callek has been working hard to finish up SeaMonkey 2.1 and get it to build, watch out for an announcement of a Release Candidate very soon!
Entry written by KaiRo and posted on May 10th, 2011 18:04 | Tags: L10n, Mozilla, SeaMonkey, Status | 4 comments | TrackBack
well KaiRo, there may be a "pending" 2.0.15 release coming because bug 646460 wasn't fixed in time for the SM 2.0.14 release: