Calendar:0.3 Release Status
We are in STRING FREEZE
Sunbird and Lightning are aiming for a simultaneous release of their 0.3 versions in October 2006. This page is meant to provide an overview of the status of that release.
The 0.3 releases are intended to provide a stable upgrade for users of all previous Sunbird, Lightning, and Calendar versions.
Key Development Areas
- Viewing of events
- Visual Alarms
- ICS Export
- Calendar Subscriptions
Viewing of Events
Sunbird and Lightning will display all events and tasks with the correct information and in the correct places.
|P1||Events/tasks are displayed on the correct day in month/multiweek view||Complete|
|P1||Events/tasks are displayed at the correct position (based on time) in day/week view.||Complete|
|P2||Tooltip information for events should be correct.||Complete|
|P3||Tooltip information for tasks should be correct.||Complete|
|P2||Unifinder should show correct information||Complete|
|P2||Events/tasks should not appear in views where they are not intended to appear||Complete|
Sunbird and Lightning should allow users to move to any display they want.
|P1||Functional navigation buttons should be available in all views||Complete|
|P1||Minimonth navigation should work.||Complete|
|P2||Navigating to distant future and distant past should be possible||Complete|
Sunbird and Lightning should visually display alarms when they are scheduled to fire
|P1||Users should be able to set an alarm for an arbitrary length of time before an item.||Complete|
|P1||Alarms should fire when scheduled, if Sunbird/Lightning is open||Complete|
|P2||Missed alarms should fire when Sunbird/Lightning is reopened||Complete|
|P2||Dismissed alarms should not re-fire||Complete|
|P2||Alarms should correspond with the ICS Standard.||Complete|
|P2||Alarms for recurring events should fire for each occurrence||Complete|
|P3||Multiple alarms should be displayed in a single window||Complete|
|P3||Alarms should be able to be snoozed.||Complete|
Sunbird and Lightning should provide a way for users to export their data in a standards compliant format. This allows users to not need to enter a 'walled garden' when using Sunbird/Lightning
|P1||Export should serialize all data into the file||Complete|
|P1||The exported file should comply with RFC2445.||Complete|
|P2||Export of particular items/sets of items should be possible. (Sunbird)||Complete|
Sunbird and Lightning should provide an easy to use way for users to get their data in a paper format, through their printer.
|P1||Printing a list of items should be possible.||Complete|
|P2||Printing a month grid of items should be possible.||Complete|
|P3||Extensions should be able to provide additional printing formats.||Complete|
Sunbird and Lightning should allow users to publish their calendar information to a web server.
|P1||Publishing an entire calendar to an http server should be possible||Complete|
|P2||Publishing an entire calendar to an ftp server should be possible.||Complete|
|P2||Publishing a specific set of items should be possible. (Sunbird)||Complete|
|P2||Published data should comply with RFC2445.||Complete|
Sunbird and Lightning should allow users to easily get information about the relevant public holidays in their area.
|P1||Subcribing to a holiday file should be possible||Complete|
Users should be able to subscribe to calendar files that have been published on the web
|P1||Subscribing to a public ics file should be possible||Complete|
|P2||Subscribing to a password-protected calendar should be possible||Complete|
|P2||Subscribing to a calendar from behind a proxy should be possible||Complete|
|P2||Standards compliant data should always be successfully read/preserved.||At risk|
|P3||Errors in standards compliance should be gracefully handled.||On track|
Users should be able to use Sunbird/Lightning with confidence that their data will be preserved.
|P1||Shutting down the application should preserve all data.||Complete|
|P1||Editing an item should work as expected.||Complete|
|P1||Subscribing to a calendar with unexpected data should preserve the data||At risk|
|P2||Standards compliant data should be preserved when edited.||At risk|
Users upgrading from past versions should not notice significant loss of functionality/usability.
|P1||"Misc Regressions" is provided to give it visibility during discussions. Individual elements do not exist at this time.|