THIS DOCUMENT IS STRICTLY A DRAFT! DO NOT MAKE PLANS BASED ON IT! NO ONE IN THE CALENDAR TEAM OR MOZILLA HAS BLESSED IT! IT IS BUT A FIGMENT OF ONE TROUBLED PERSON'S IMAGINATION!
Much work has been done to both define and synchronize the roadmaps of Sunbird and Lightning. This work is by no means complete, and given the evolving nature of software, will likely never be. Regardless, in order to help drive both projects, this tentative and historical roadmap has been created.
For the fullest understanding of this document, and some context as to why some features are slated for which timeframe, it is useful to review the defined target users and their use cases, as well as our previous releases.
"Where's the 0.n meta bug?"
Note that we have transitioned to using blocking flags to keep track of release blockers, rather than tracking or meta bugs. See the document on Blocking Flags for more details.
One of our goals is to incorporate user feedback as much as possible. Nightly builds, however, might have an unclear status regarding their functionality and thus are not useful for a broader audience. Instead we want to release milestone builds every 3 months which will cover an appropriate part of the road map. Those milestone builds will have gone through QA to make sure that they are suited to generate useful feedback. In order to reach a good balance between being in development-mode and being in release-mode we're heading towards Version 1.0 within 4 milestones.
|M1||0.3||Early Access||Align Sunbird and Lightning, beginning of UI face lift, iTIP/iMIP||August/September 2006|
|M2||0.5||Beta||Most features should be visible||November/December 2006|
|M3||0.9||Beta2||Incorporate beta feedback, shift uncomplete features to 1.x||February/March 2007|
|M4||1.0||Final||Bugfixing only||May 2007|
Lightning and Sunbird 0.3
It was decided to synchronize Lightning and Sunbird in terms of bug fixes, feature set (where applicable), version number, and release timing.
The goal of the roadmap is to stay high-level enough to provide adequate direction, but still stay low-level enough to provide relevance. The goal is not to list specific bugs to be fixed before release. Please use blocking flags for that.
We must make sure that Sunbird 0.3 is a linear step forward from 0.2. This is a challenge that the Sunbird 0.3 alphas have not yet met. Achieving this will not only decrease the number of Sunbird 0.2 support problems, but will also help encourage migration from the deprecated Calendar XPI to Lightning, since the parallels will be clearer.
Since the average user is generally not interested in the specifics of which bug numbers got fixed this time around, we should have some tangible features we can point to that justify the release.
The 0.3 alphas received much user praise due to the stability provided by the new storage, and the increased speed of the XBL-based views.
This time around we can also point to
- Improved speed (snappiness™)
- Restructured recurrence
- Better l10n story (language packs)
- No known dataloss with ICS from *any* source (preserve X-Comps/X-Props, handle foreign timezones)
- Bug fixes from previous releases
- Improved task support (recurrence)
- Continue to sync code between Sunbird and Lightning
- Fix/improve CalDAV
- Safety when multiple users edit a calendar (maybe)
- Feature parity with Sunbird
- Dog-food iTIP/iMIP
- Be a Modern toolkit app (prefs, installer, l10n, etc., but no auto-update yet)
- Feature Parity with 0.2 (calendar loading, offline use?, printing, multiple selection - "Select All")
Commentary: The bits in parens are only met to be examples for clarification. They are not exhaustive or definitive lists and should not be considered part of the actual roadmap.
Parts of this list seem to be reaching a bit far (offline use, multiple edit safety), but according to the current agreements, we're only going to have a few releases before 1.0, which means we need to front-load a bit more if we're going to have a chance of meeting that.
Lightning and Sunbird - Future Ideas
New features and their order of implementation and release will be mostly driven by the previously defined, and constantly refined target users and their use cases
Disclaimer: These are entirely ideas. Don't bet the farm on the fact that they're listed here. They may, and some likely will, never actually make it into a shipping product. They also are likely too low-level for the actual roadmap, but may encourage thought around future higher-level goals.
- Make Sunbird a child app of XULRunner.
- Integration with Mozilla Software Update.
- Possible view eye candy using Cairo?
- Ability to consume Google Gdata?
- Merge Lightning and Sunbird into a single entity that acts appropriate depending on the host app it is running under?
- Better Thunderbird integration
- email<->task linkage
- iMIP support
- Improved CalDAV support
- Cached calendar support for offline
- Device synchronization