The roads I take...

In previous years, when we had a public security or grave stability problem in a "stable" release and needed to go into fast-pace mode to get update out as fast as possible to fix that, we called that a "firedrill". Still, that name is not very accurate, as it's a real problem case, not just a drill for one.

So, recently, Mozilla land adopted the name "chemspill" for those - needing to clean up after spilling chemicals represent the actual case better for sure.

But then, after recent events, I realized that for maritime life-forms like Sea-Monkeys, it's really more fitting to call it an "oilspill" in our project. Thank goodness, we didn't need that expression for quite some time after I came up with it - until now.

With SeaMonkey 2.0.7, we saw a sudden rise of a previously-rare crash signature in our topcrasher statistics, along with comments from users that it was on launch after updating that this happened, and the affected users were not able to run SeaMonkey at all any more in this version. Now, that's unacceptable, of course, so we stopped issuing updates from 2.0.6 on the release channel and went into investigating the problem.

It turned out that we had both a problem on our side with cleanup after updates as well as a platform problem that affected Firefox and Thunderbird as well, and it looks like both together were even worse for us. We found fixes for both now and decided to take a fix for font face in HTML email signatures along for the ride on creating a fast update that has nothing but those changes in comparison to the 2.0.7 release.

We now have candidate builds of this SeaMonkey 2.0.8 version up for testing and will ship it to the public between today and Friday of this week if everything looks as good as expected with it.

So, after all, we have our first "oilspill" release situation on our hands and I hope we are dealing with it in a satisfactory way. I just wish that real oil spills would be as easy to deal with as those in our software.

Now, how cool is that?

The Firebug team just announced that their 1.5 version is now available from the addons-mozilla.org ("AMO") website - and this version even supports SeaMonkey 2.0 now!

You don't believe it? Look here:

Install Firebug 1.5 in SeaMonkey 2.0

I have already tried and installed it from their website before, and I have it just right in my browser windows now! I haven't tried it yet, but it has a few things that look interesting, I surely will dig into it when I have time, I already heard a lot of praise about this development tool from the Firefox world, and now I can even use it!

So, after Lightning, we have another one of the big Mozilla add-ons work in SeaMonkey 2.0 - I hope that's the real start for a solid success story now.

Once again, this has been enabled by someone from our great SeaMonkey community, in this case Jens Hatlak (InvisibleSmiley), thanks a lot for testing and writing up patches for this. Also a big "thank you" to the Firebug team for taking those patches quite fast and even convincing AMO that our application suite is really supported!

You might already have read about the release of Lightning 1.0 Beta 1 - maybe you even remember my earlier posts about SeaMonkey 2 and Lightning. And now here's the good news, right from the announcement the calendar team made:

You can install Lightning 1.0 Beta 1 from AMO and manage your calendars now directly from within the SeaMonkey Mail & Newsgroups component.

We have been working closely with the calendar team to make Lightning work as well as possible within SeaMonkey, but we're also sure things can be improved further, and any help is appreciated.
Also, both the SeaMonkey and calendar teams appreciate testing of this Beta and reporting bugs, so we can make your calendaring experience with SeaMonkey and Lightning even better in the future!

Here's a bit of an overview of press articles we got for the SeaMonkey 2.0 release. The English and German ones were collected by myself (we were pretty well-featured in German media), the French and Czech ones come from our respective localizers, Cédric and Pavel.
I've hidden two "easter eggs" in the English list that could help some of our users, by the way - a forum thread for ubuntu users (things are easier for some other Linux distros - openSUSE offers it in the build service and in upcoming openSUSE 11.2, and upcoming Fedora 12 also has SeaMonkey 2.0) and a link to the portable version that is available now.

English:

• theregister.co.uk: Mozilla's SeaMonkey 2.0 exits cryptobiosis
• cnet.com: Mozilla releases SeaMonkey 2.0
• mozillalinks.org: SeaMonkey 2.0 is here!
• slashdot.org: Mozilla Releases SeaMonkey 2.0
• lwn.net: SeaMonkey 2.0 released
• linux.com: Mozilla SeaMonkey 2.0 Released
• ubuntuforums.org: Seamonkey 2.0 released, ubuntuzilla needs tweak
• portableapps.com: SeaMonkey, Portable Edition
• it-chuiko.com: SeaMonkey 2.0 is ready
• internetnews.com: Mozilla SeaMonkey FINALLY hits 2.0
• h-online.com: Mozilla releases SeaMonkey 2.0
• ostatic.com: Mozilla Delivers SeaMonkey 2.0
• lifehacker.com: Mozilla SeaMonkey Updated to 2.0
• majorgeeks.com: SeaMonkey 2.0 Final
• maximumpc.com: SeaMonkey 2.0 Now Available
• applelinks.com: Mozilla SeaMonkey Project Releases SeaMonkey 2.0
• kabatology.com: Seamonkey 2.0 Released
• findmysoft.com: The New Features and Enhancements in SeaMonkey 2.0
• esoft.web.id: Mozilla SeaMonkey 2.0 Final: All you can do on the Internet you can do with SeaMonkey
• v3.co.uk: Mozilla SeaMonkey 2.0

German:

• heise.de: SeaMonkey 2.0 erschienen
• futurezone.orf.at: SeaMonkey 2.0 erschienen
• derstandard.at: Seamonkey 2.0: Mozilla-Nachfolger in neuer Version
• golem.de: Seamonkey 2.0 ist fertig
• pcwelt.de: Seamonkey 2.0 steht zum Download bereit
• zdnet.de: Mozilla veröffentlicht Browser-Suite Seamonkey 2.0
• winfuture.de: SeaMonkey 2.0 - Nachfolger der Mozilla-Suite
• pro-linux.de: Seamonkey 2.0 fertiggestellt
• linux-magazin.de: Browser-Suite Seamonkey 2.0 ist da
• webmasterpro.de: Mozilla Seamonkey 2.0 ist fertig
• t3n.de: Internet-Alleskönner Mozilla Seamonkey 2.0 ist fertig
• pc-professionell.de: Seamonkey 2.0 ist da
• macgadget.de: SeaMonkey 2.0 ist fertig
• tecchannel.de: Mozilla schließt kritische Lücken in SeaMonkey

French:

• 01net: Logiciel libre : SeaMonkey 2.0 à télécharger
• PC Inpact: SeaMonkey : une montagne d'améliorations pour la version 2.0
• Linuxfr: SeaMonkey 2.0 la suite Internet
• Silicon.fr: Navigateur web : la suite SeaMonkey 2.0 est en ligne !
• Generation NT: SeaMonkey : la suite Internet en version finale 2.0
• Clubic: Le navigateur tout-en-un SeaMonkey disponible en v.2.0
• PC Boost: SeaMonkey, le navigateur tout en 1, disponible en version 2.0
• Mac Generation: SeaMonkey passe la seconde
• Mac4ever: SeaMonkey : la suite communicante de Mozilla en version 2.0

Czech:

• mozilla.cz: Vy¨lo SeaMonkey 2.0!
• czilla.cz: SeaMonkey 2.0
• root.cz: Vy¨lo SeaMonkey 2.0
• lupa.cz: Přichází SeaMonkey 2.0, seznam novinek je dlouhý
• root.cz: Přichází SeaMonkey 2.0
• abclinuxu.cz: SeaMonkey 2.0
• slunecnice.cz: SeaMonkey 2.0: To nejlep¨í z Firefoxu a Thunderbirdu
• extrawindows.cz: Novinky: SeaMonkey 2.0, Simple Adblock, Unlocker a dal¨í
• mozilla-europe.org: SeaMonkey 2.0 - Moderní balík internetových aplikací je tu!

Oh, and here's a scanned image from the German IT magazine - c't (Edition of October 26th, page 52):

It's about RC2, but still cool to be present in that magazine...

Das SeaMonkey-Projekt aus der Mozilla-Familie freut sich, heute seine komplett überarbeitete nächste Generation des "Alles-in-einem"-Internetpakets zu veröffentlichen: SeaMonkey 2.0 ist jetzt zum kostenlosen Download verfügbar und verschmilzt die Ideen hinter dem Netscape Communicator mit der modernen Plattform von Firefox 3.5 zu einem der überzeugendsten Open-Source-Produkte für fortgeschrittene Internetbenutzer.

Die Kombination von Internet-Browser, E-Mail- und Newsgroup-Programm, HTML-Editor, IRC-Chat und Web-Entwicklerwerkzeugen, die schon in ihren Vorgängerversionen eine breite Benutzerbasis etablieren konnte, wurde auf der modernen Mozilla-Plattform neu aufgebaut, die neben anderen Funktionen eine hervorragende Verwaltung für Erweiterungen (Add-ons) bietet.
Zusätzlich wurde sie weiter verbessert, beispielsweise mit Feed-Unterstützung (inklusive eines RSS- und Atom-Feedreaders in der Mail-Komponente), einem modernen Aussehen, Wiederherstellung von Browser-Tabs und Fenstern nach Abstürzen oder Neustarts, Mail-Tabs, automatischen Updates, intelligenter History-Suche aus der Adressleiste, schnellerem JavaScript, HTML5-Funktionen (wie Video oder herunterladbare Schriftsätze) und sogar Unterstützung für die Kalender-Erweiterung Lightning (von der eine Beta-Version zur Installation in SeaMonkey 2.0 innerhalb der nächsten Wochen erwartet wird).

Die Release Notes (Versionshinweise) enthalten eine detailliertere Liste der Verbesserungen und bekannten Probleme mit der neuen Version, sowie Installationsvoraussetzungen und -anleitungen. Weitere Informationen über SeaMonkey 2.0 und das SeaMonkey-Projekt erhalten Sie auf seamonkey-project.org bzw. der deutschsprachigen Seite seamonkey.at!

Some of you might remember that I was planning for an OpenWebCamp in Vienna - that was planned for October 27 but it was downgraded seriously due to not having a real Mozilla community around here yet and me not being able to organize the event myself when driving a major release at the same time. Still, the guys from quintessenz planned to have us on board for a track of the Cyber Liberties Conference, and so I did sit down with them for a while this week to work out what we actually can get into this track (speakers still wanted, if you can come around to talk on open web topics in Vienna on short notice, please tell me, travel costs can probably be reimbursed).

In any case, I told them that we're planning to release SeaMonkey 2.0 final right on that day, and the guys were suddenly cheering! We could do an official release event right there, they claimed, we could add this into press releases - and, above all, this could finally the topic they have been looking for as a label for the party on Monday!

In the end, what we decided there is the following:

• October 26, 20:00: q/Treff Spezial @ q/uintessenz - Museumsquartier Wien: Seamonkey 2.0 Release Party
• October 27, Open Web Camp/Track @ Cyber Liberties Conference, with a number of talks on Mozilla and the open web - and with an official SeaMonkey 2.0 Release Event

If anyone reading this is from or near Vienna, I'd be very happy to meet you at any of those events next week!

It's been some time since I blogged lat about SeaMonkey statistics, and as the bouncer download data feed is hosed once again but we have two betas out, I was interested myself in some numbers of how we are doing.

Daniel Einspanjer from the Mozilla Metrics team was friendly and sent me some data he could gather from their systems last week (he says he'd be glad if someone from the community with webdev knowledge would come up to help making a public interface for such data - a blog post from him will come soon).

So, let's look at some graphs:


The first one depicts SeaMonkey downloads through downloads.mozilla.org in 2009 so far, excluding auto-update downloads for 2.x versions - blue areas are 1.1.x, green areas are 2.0 alpha/beta.
Of course, the stable 1.1.x ranks much higher than the 2.0 alpha/beta versions, and both naturally show spikes on release days. It's interesting that we got about the same number of 2.0 beta 2 on release day as for beta 1, esp. in the light that automated updates don't show up here, so that's new installations usually. Also, the daily level after the release spike is significantly higher for the betas than for the alphas, which is probably expect but nice to see here as well.
As a note, the 1.1.16 downloads visible in the graph sum up to about 380,000 total, 1.1.17 to about 340,000 - both are only for the main en-US downloads, no localized versions counted for 1.1.x - contrary to 2.0 betas, where localized downloads are also counted now.



The second graph shows daily users as estimated from add-on blocklist pings. As only SeaMonkey 2.x support the new add-ons system, the data can only take those into account here, we don't have this data for 1.x. Blue areas are official alpha/beta releases, turquoise areas are nightlies or self-built 1.9.1-based versions (with a -pre identifier), the green area is experimental mozilla-central-based 2.1a1pre self-built or nightly builds.
The graph shows that we have a stable pool of somewhat under 1000 nightly users, they probably hit their highest point at the end of the alpha period and decreased slightly with betas - looks like some people found the betas more usable than the nightlies after all.
We had a continuously rising user base all the year, though growth almost stagnated during summer in the late alpha 3 period - only to start a significant steady increase once the first beta hit the public. That increase still goes on today, hitting over 5600 daily users on Sep 22 and 23, the last two days in this data set, over 3800 of those users are on 2.0 beta 2.
And remember, all this is daily users on prereleases, as we don't have a stable version with support for add-on blocklists yet.



Finally, here's a look at what percentage of those daily users are on what locales, for both betas (which were the first versions shipped in multiple languages).
The huge blue chunk is US English, of course, accounting for slightly over 2/3 of our users on those versions. A comparison with Firefox numbers suggests that this would decrease as we add more locales in the future. The largest localization is German (green) with about 17% of our user base, followed by Russian (pink) with roughly 6-7%. In beta 1, Czech (yellow) had 3% - losing it for beta 2 was somewhat unfortunate for that reason, we sincerely hope it will be back for RCs and final! Polish (red) and French (light green) are used by about 2% of our users, and European Spanish by about 1%, all others have lower usage. I hope we'll add a few locales in the future that will show up with potentially high numbers. Still, this data is all for betas, but interesting nevertheless.

I hope those statistics give you a good look into what's going on with SeaMonkey in terms of downloads and users. I think we are on a good way with 2.0, and I'm surely looking forward to seeing how a final 2.0 will hit the road and those statistics!

I've seen a stream of new comments on my older SeaMonkey and Lightning Calendar" post, so I think I should provide you with a bit of an insight of where we are with this now - after all the official SeaMonkey 2.0 Beta 2 announcement mentions Lightning.

The good news is that you actually can install current Lightning 1.0pre nightlies in SeaMonkey 2.0 Beta 2 and above and you will get a lot of calendaring functionality right in your suite install.

The bad news is that not everything works yet, see the open Lightning-SeaMonkey integration bugs for an overview.

The most notable problems are the invitation feature not working and no access to Lightning preferences.

We are working on solution for both of those and more, some work needs to be done in SeaMonkey code, some in Lightning code, but patches are coming up and we hope to have at least our side, hopefully also their side, fixed when we ship release candidates for SeaMonkey 2.0 and even more the release itself.

Note that all the general points I raised in the original blog post on this topic are still true, neither official Lightning releases with SeaMonkey support nor shipping SeaMonkey with this calendering functionality by default are planned right now, it's all about making it possible at all to install Lightning at all and making it work well enough that people can test that combination more thoroughly.

At the SeaMonkey and Thunderbird meetings this week, I started advocating for the SeaMonkey 2.0 schedule to be decoupled from Thunderbird 3.0, specifically, to have SeaMonkey 2.0 Beta 2 and final be released before their Thunderbird "counterparts".

For some fun around this, let's view a proposal of a schedule I sent to the SeaMonkey Council in mid-December 2008:
We actually did release Alpha 3 on March 3 and Beta 1 on July 21, and added a second beta that is still to be released, apart from the fact that Thunderbird plans changed significantly as well. I don't really know if I should laugh or cry when reading that proposal from 7-8 months ago.

So, what went wrong or not as expected? For one thing, there is this old rule that every project takes longer than expected, even if you plan with that circumstance in mind. For the other, we decided to follow Thunderbird schedules so that freezes for the shared mailnews code code are aligned and we cause each other as few problems as possible. And that turned out to be the wrong thing to do for the SeaMonkey project, because the objectives the two projects have for the upcoming release series are quite different and therefore impose different scheduling.

Thunderbird has a new team that took over after a period where development stalled, and they try to show off that things are moving as well as make the product better fit for the mass-market.
SeaMonkey has the team that has been in charge for some years now, where it did continuous development, and we try to get our existing userbase to a new level while making the product more compelling to the same target audience as before

Thunderbird's current stable release is built on top of the "new toolkit" platform also used by Firefox, including good add-on management, mail and news standards haven't seen significant new features, and their security updates are driven by MoCo on well-managed, redundant release infrastructure.
SeaMonkey's current stable release is built on top of the "old xpfe" platform inherited from Mozilla Suite, with quite bad add-on management, the web sees lots of new developments in standards, and I need to manage our security updates myself, building them on my private machines that definitely show their age and have zero redundancy.

On top of that, Thunderbird has multiple people working full-time on the project, so that they are able to hand off management of releases where needed and have some organizational redundancy while in SeaMonkey land I'm the only one working full-time on the project and doing all release management and build engineering work without real redundancy.

And then, I have booked the flight for a three-week vacation in November, believing this to be far from any release. There I need to get off my thoughts from day-to-day work, have enough breathing room to really have some fun and appreciate the beauty down in Dixie so that I can "recharge my batteries", figuratively speaking. The last thing on my mind there is a major release that still need to be completed even though it should have been out for half a year.
I don't think I'd manage to really relax with an unreleased 2.0 on my mind, and that would probably leave lasting damage to my mental health, which I would like to prevent.

Given all that, I convinced the team at the SeaMonkey Status Meeting to target a freeze for Beta 2 on September 1 and assure that we will release final before November. We will re-evaluate the target freeze date in the next meeting on August 11 and make firm schedules there - but remember that a code freeze for that last beta also means a feature freeze for the whole 2.0 series!

This might mean that we possibly won't get everything into 2.0 that we would have liked to have there, but we are in no way short of total improvements in this series, and it's time we get something better than 1.1.x out to our regular users. There will be further releases, hopefully with smaller steps, following the "release early, release often" methaphor that's proven to be successful in open source projects overall.

I would have liked to sync up with Thunderbird as freezing shared code at different times can be somewhat painful at times, but given the different objectives, they seem to be less pressed by time and more pressed by features, while we already have a big load of features to show off in this release, but are overdue to deliver something.

I hope things work out fine that way and I'll blog again when we know even more on concrete schedules.