Software production is a lot like sausage factories. The end result is nice, but peeking behind the factory walls isn’t always pretty (cue scene from Tintin in America).
It’s been educational to go through the process of picking nominations for the next alpha release, understanding the interactions between Gecko changes and the impact on Thunderbird, and more. We’re getting there, though, as soon as we can figure out a couple of last issue. But then there’s the issue of “public perception”, in particular what we should call this next release. Because names are loaded, and version numbers even more so.
So what is the point of doing this next release? There are lots of somewhat conflicting goals:
- Because it’s time: it’s been a long time since there was any non-security release of Thunderbird, and that’s always dangerous. Software that’s not used by people outside the inner circle tends to have hidden flaws that get harder to fix with time. So it’s important to release something, anything.
- Because we’re on trunk: Thunderbird development has been going on on the “trunk” of Mozilla for several months now, and as a result a lot of changes motivated by both the evolution of the platform and Firefox 3 have impacted Thunderbird. It’s good to get feedback on the consequences of those changes, whether that’s cool new features like the Add-on manager or core changes like the changes in the widgetry on the mac.
- Because it’s a new team. The Thunderbird 2.0.0.x releases you’ve seen over the last few months have all been done by the Mozilla Corporation engineers who have those processes ironed out. Some of us on the Mozilla Messaging side are new to making Mozilla releases, and it’s certainly better for everyone if we work out the kinks in releases doing early releases rather than “important” releases. At the same time, having a new team means that we can challenge some of the old ways, and consider doing things differently because the environment is different.
- Because we want to release often: Both Dan Mosedale and I really want us to move to a more agile development model, where releases aren’t that hard, and where we can experiment with changes without huge impact on the QA process. That’s going to be hard, and involve investments in all parts of the pipeline, from build automation (Rick’s on that), to unit test coverage (Mark’s on that), to rethinking how we do QA (Gary and Wayne are on that). But getting there also means understanding, documenting, and streamlining the release process.
- To re-engage with the add-on developer community: there’s lots of work to do to make sure that when 3.0 is ready, the add-on community has been part of that process, so that their extensions can be ported to the new codebase. Having a release that they can target that is based on trunk is a good first step there (finishing and documenting STEEL is another big step in that direction).
Note that there’s a big reason to release which isn’t mentioned above, and that’s “to get feedback on the big changes in the next major release of the product”. And that’s because none of the big changes that we’re hoping to have in Thunderbird 3 are in this build. So for most users, I expect that the differences between this next release and Thunderbird 220.127.116.11 are going to feel pretty minor. Which is how it should be at this stage.
However, given how long it’s been since there’s been a feature release, it’s likely that if we label this release “Thunderbird 3.0a1”, that we’ll both get complaints about how little has changed since Thunderbird 2, as well as give the impression that we’re close to nailing down Thunderbird 3, neither of which are true.
Furthermore, we really do mean that it’s an alpha release. There are no guarantees, there will be minimal testing, and it’s possible it will eat up all your mail (although unlikely =). So calling it Thunderbird anything is likely to confuse people who don’t follow Mozilla closely.
Given all that, I’m thinking that this next release should be called Shredder a1, with Shredder (Rick Tessner’s brainstorm) being to Thunderbird what Minefield is to Firefox. We probably won’t have the word Shredder in the product for a1, but hopefully for a2.