User:Dmose/Tb Post-3.1 Scratchpad

	THIS PAGE IS A WORKING DRAFT
	The page may be difficult to navigate, and some information on its subject might be incomplete and/or evolving rapidly. If you have any questions or ideas, please add them as a new topic on the discussion page.

At the moment, this page is merely a scratchpad where I'm putting together ideas for post Tb3.1 work.

After things on the Tb Post-3.0 Scratchpad have solidified a bit, we'll work on defining and moving forward the things discussed here.

UI Iteration Via Extension

We did some UI iteration in extensions in Thunderbird 3, with varying degrees of pain-upon-landing. The big win, it felt like, was the ability to get UI to a workable and understood state before imposing it on everyone using nightly builds. We'd like to explore this methodology more going forward, but we'll need to nail down more details about our process and what sorts of experiments with it that we'd like to do. In particular, we'll need to think about how we handle:

• UI-review
• code-review
• test writing
• l10n

such that things happen in appropriately sized chunks at the right time. Bryan has drafted a basic proposal for moving forward with this, and that will see wider discussion shortly.

Feature & Component Roadmaps

Rather than having a single big roadmap that then ends up having lots of things cut from it at the end, davida has suggested that we instead have individual roadmaps for different feature and code areas, particularly those where we can avoid a lot of cross-dependencies. We can then pick appropriate pieces of work from various different road maps and target them at a given release, and if some don't make the release they're originally slotted for, it doesn't disrupt the overall roadmap for that release.

Features and components are likely to vary significantly in how much they evolve versus are mapped out in advance.