441
edits
No edit summary |
|||
| Line 61: | Line 61: | ||
=Future Releases= | =Future Releases= | ||
'''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 [[Calendar:For_Everyone:Blocking_Flags|Blocking Flags]] for more details. | |||
==Lightning and Sunbird 0.3== | ==Lightning and Sunbird 0.3== | ||
As mentioned earlier, 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 [[Calendar:For_Everyone:Blocking_Flags|blocking flags]] for that. | |||
===Key points=== | |||
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) | |||
=== Common goals === | |||
*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) | |||
=== | === Lightning === | ||
*Feature parity with Sunbird | |||
*Dog-food iTIP/iMIP | |||
*Localization? | |||
=== Sunbird === | |||
* 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== | ==Lightning and Sunbird - Future Ideas== | ||
| Line 98: | Line 106: | ||
[[Calendar:Task_Feature_Matrix|target users and their use cases]] | [[Calendar:Task_Feature_Matrix|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. | '''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. | * Make Sunbird a child app of XULRunner. | ||
edits