jminta's comments
As per IRC discussion, I'm not very completely comfortable with the 0.3 goals listed here. They range from somewhat high-level all the way down to bug-level. In my opinion, roadmaps need to stay out of bugzilla as much as possible. (When was the last time you saw a bug # in a firefox roadmap?) However, we've now been operating for a fair bit of time without a lot of direction, which decreases productivity and increases frustration. As such, I'd like to go ahead and give my own list of proposed high-level goals for 0.3 in both Sunbird and Lightning.
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 Sb and Ltn
- Fix/improve CalDAV
- (maybe) Safety when multiple users edit a calendar
Lightning
- Feature parity with Sunbird
- dog-food iTIP/iMIP
- Localization?
Sunbird
- Be a Modern toolkit app (Prefs, Installer, l10n, etc)
- Feature Parity with 0.2 (calendar loading, offline use?, printing, multiple selection)
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.
I still think we need to make sure that Sunbird 0.3 is a linear step forward from 0.2. This will not only ensure that we will rarely deal with 0.2 support problems, it will also help to encourage migration from the calext to lightning, since the parallels will be clearer.
Parts of this list seem to be reaching a bit far (offline use, mutliple edit safety), but according to the current agreements, we're only going to have a couple 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.
During release time we can also point to
- Improved speed
- Restructured recurrence
lilmatt's comments:
jminta: I took most of your stuff and included it verbatim. I waxed poetic on the "tracking bugs vs. blocking flags" subject, and then decided it was best to split it out to its own page.
Feel free to tweak.