Thunderbird 3 beta 2

On the road to Thunderbird 3, another milestone — this time, Thunderbird 3 beta 2.


Why do beta releases?

Beta releases are funny things. They serve a few purposes. The first is to make sure that we periodically stabilize the code base, as without periodic ‘cooling’, it’s hard to get a handle on the quality of a piece of software. Betas also serve as deadlines, which are magical motivators for some people. Some of us will spend way too many hours staying up late in the night in order to “make a deadline”.

Betas for open source software are even more odd in that people interested in staying very involved with the project can use nightly builds, which are updated every day. I’ve been using nightly builds of Thunderbird for over a year, as have several thousand other users. As a user of nightlies as much as a project coordinator, by the time the beta is released to a wider audience, all the excitement is historical.

Another fascinating aspect of beta releases is that, because we know there will be another release, and because the purpose of the beta is to get a broader set of testers to shake out edge cases, we try to be conservative about slipping in major features at the last minute, as the odds of those features being polished in time are never what we hope they’ll be. So we routinely delay feature additions until the next cycle, to avoid dragging the beta validation process out. It’s an unpleasant, but unavoidable part of optimizing releases.

If we do our job right there, then by the time the beta ships, the features that have landed are free of major bugs. We of course can’t know that until we get feedback from the beta.

What’s in this release?

The most striking part of the release is the sheer volume of bug fixes. It’s not sexy work, it’s often the hardest work, but it’s very important. This list (of bug fixes and feature work, but mostly bug fixes) is impressive.

Of the features that have landed, I want to talk about two that many users could easily ignore: archiving, and the activity manager.

The archive feature is straightforwardly borrowed from GMail’s archive feature, which we think is great. The idea is that figuring out exactly which folder each message should be filed is a process that can take a lot of time and effort — something that wasn’t a real problem in the early days of email, but which becomes a real time sink with thousands of messages. With a good enough search engine, it’s easier for many users to simply “archive” the message (doesn’t really matter where), get it out of the way, and then rely on the search capability to find the message again.

In this beta, we’re half-way there. The archive feature is there if you want it, but you can also use the standard “file in a folder” method. Thanks to work we did before beta2, the archiving is fast, putting messages in per-month folders at the click of a buttton or a keystroke. The new fast global search hasn’t landed yet, but even our “old” cross-folder search mechanism has gotten a lot better.

I already love the feature — being able to select messages I don’t need to worry about anymore, hit ‘A’ and be done with them, saves me a lot of time and mental effort

The second feature worth highlighting is also not fully deployed, but already useful. The Activity Manager was born out of a recognition that Thunderbird 2 is pretty bad at telling you what it’s doing. It says a lot of things, it says them fairly loudly, but they’re rarely the things you want to know. We’re building infrastructure that will let the various bits of Thunderbird be much more helpful in describing what’s going on (through a log of notable events), what went wrong (non-intrusive but notable alerts), and how it’s progressing at long-running tasks (with more context than just a single progress bar). Teaching software that wasn’t designed with a notification mechanism or philosophy in mind how to be polite and informative is a slow and arduous task, but we’re making good progress. In Thunderbird 3b2, there’s an Activity Manager window, which for now will just report on message moves, copies and deletes, and IMAP auto-syncing. Now that the framework is in place, we should be able to have a lot more informative messages when you need them, and reduce the number of dialog boxes (especially the ones you can’t do anything about!).

One of the fascinating aspects of the activity manager is that it’s giving even those of us who know how the software works on a detailed level a better handle on important global aspects. For example, the activity manager showed me that the autosync function can and should be much more aggressive, so that more of your email is already downloaded before you need it.

Other features you may notice:

  • Much more useful Growl notifications on OS X
  • Keyboard shortcuts for quick tab navigation
  • Better looking forwarded mail
  • Fewer dialog boxes

What’s next?

The next beta release is our last scheduled beta. As such, we’re thinking of it as the last milestone to introduce Big New Features. Furthermore, we’re hoping to be even better behaved this cycle and land features as early in the process as possible. Upcoming features which we hope will be available in a nightly build soon include:

  • the new global search function, leveraging tabs
  • cleaning up the message header area further
  • “pop tarts” to complement the activity manager
  • the beginning of some theming work (prettier icons, etc.)

And then, of course, there will be unplanned bright ideas which show up out of nowhere. Life wouldn’t be fun without those.

Try out the beta, file bugs, send feedback!

PS: the illustration at the top is from a brand spankin’ new website for Mozilla Messaging. We’ve changed the site to make it the primary destination for Thunderbird users, riffing on the look of other Mozilla websites, and yet quite distinct. I find the illustrations in particular a lot of fun, and I’m very proud of the team that built it. Rafael Ebron ran the project with the SpreadThunderbird team, with designs from The Royal Order, and implementation from silver orange. A very nice job, thanks to all who contributed!  The new site also allows us to build localized sites, which will be amazing.

Positive Energy for Change, for a Change

Change is hard. I spend a lot of time trying to enable, encourage, foster, stimulate, provoke, change in software.

Part of that is because it feels like it’s that most plastic of human endeavors. That, of course, is only true to the extent that the people involved in the creation of software _are_ plastic.

One of the fascinating things in the last few months is that it feels that, with the Obama administration, people are thinking big about societal change, in a variety of contexts.

The latest one to cross my twitter stream is Carl Malamud’s bid for the government printing office, which is full of great, big ideas. So cool.

Read up about it:, and follow the links to the proposals & the videos. They’re quite compelling, optimistic, ambitious, and, I’m sure, threatening to the status quo. At the very least, it’s a great conversation.

Godspeed, Carl.

Lightning-in-Thunderbird status update

For some time, we (the Thunderbird release-drivers) have been exploring how to best integrate calendar functionality into Thunderbird.  Time for an update.

The current plan is to work with the Lightning Add-on community to make a version of it available as an add-on to Thunderbird 3 after we ship later this year.  This is a change from our initial plan of integrating all of Lightning into Thunderbird by default.  Our thinking has evolved based on both technical and product reasons:

  • the calendar team has had a tough time of figuring out how Lightning needed to change to integrate optimally in Thunderbird, in large part because Thunderbird 3 itself has been somewhat of a moving target — Thunderbird’s interface model is still shifting, which is certainly hard on add-on developers
  • partially as a result, there’s a fair amount of work left to do on Lightning before it’s ready to present as part of the core product.  For example, it’s not yet possible to selectively enable the task management or calendaring features; the account configuration is a bit too hard to get right for novice users; error messages are still too cryptic — that sort of thing.
  • looking at Lightning as an addition to the core project, it would represent a lot of new, complex code, with a lot of implied maintenance — we don’t have enough developers on hand to be able to take on that commitment at this stage.  See Philipp’s post on this topic for more information, especially if you’re keen to help out.
  • we try to avoid feature changes in between major releases, and limit minor updates to security fixes.  This would mean that feature changes to Lightning would have to wait for the next major release of Thunderbird.  That would be a real shame.
  • more generally, we recognize that different users need different kinds of calendaring solutions.  Just as there are more and more messaging systems, there is a growing diversity in calendar usage models, such as web calendars, stand alone clients, and calendar and event applications on social networking platforms.

Given all this, we feel the best plan is to take advantage of our add-on ecosystem, to allow a variety of calendaring features to evolve, and to allow Lightning to evolve at whatever pace is best for it, less tied to Thunderbird’s schedule.  Lightning is by far the most popular and important Thunderbird add-on, and we’re going to see what we can do to make it better and more successful, both on the development side, as well as on the promotion side.  Also, thanks to Thunderbird 3’s new add-on manager, it will be easier for users to find and install, which I expect will lead to even greater adoption.

In short: expect a version of Lightning that will work with Thunderbird 3; expect it to have more frequent releases than Thunderbird major release numbers; talk to philipp if you want to help!