With this status update, I thought I’d try to give you some insight into what went on in preparation for the Lightning 0,1 release candidates.
As the blocking list grew smaller, it appeared that March 4 could be the date for Lightning 0.1RC1. (As you know, this didn’t happen, see below.) In the week prior to that, many small, low risk bugs were identified and patched. Examining these bugs you’ll notice that a majority of the patches were just a few lines long. There were also a fair number of changes to recurring events, to enable individual elements of recurring series to be edited.
- Bug 323093: (Both) Week/Day view should expand when events fall outside the default hours
- Bug 328084: (Both) Errors/unexpected behavior when mixing ‘Modify this occurrence’ and ‘Modify all occurrences’
- Bug 328653: (Both) Alarms set for 15 or 30 min after an event show up as 15/30 minutes before.
- Bug 328761: (Both) Alarms greater than 9 hours in advance end up at random times.
- Bug 328763: (Both) Alarms for all day events rounded up to the nearest midnight
- Bug 328632: (Both) Times displayed in alarms are ugly and include useless timezone information
- Bug 328483: (Lightning) ‘Play sound’ preference when alarms are fired does not work
- Bug 328510: (Both) Deleted exceptions to recurring events remain in data-storage, but should be purged
- Bug 328011: (Both) Create easier method for determining whether 2 occurrences are equal
- Bug 325786: (Both) No way to add exceptions to events in the event dialog
- Bug 328011: (Both) Audit code for proper use of identify testing of XPCOM objects and fix violations
- Bug 329240: (Both) Fix regression from Bug 328011
- Bug 327845: (Both) Error writing items with attendees to local (storage) calendars
- Bug 327877: (Both) Multiple entries for same task are created in agenda when editing task.
- Bug 328754: (Sunbird) Cannot create new events if default alarm for events is ‘On’
- Bug 326352: (Lightning) Bump version number to 0.1
At this point, we thought we had it. Testing the next nightly, however, revealed fallout from some checkins to the MozStorage implementation (Bug 329518). While that bug was being fixed, a few other checkins went in as well:
- Bug 328597: (Lightning) Calendars are not removed from the list immediately upon delete
- Bug 329373: (Lightning) Creating an ICS (webdav) calendar with a file:// url can fail.
- Bug 326116: (Both) Don’t download an ICS (webdav) calendar if eTags are present and indicate the file has not changed
- Bug 315511: (Both) New ICS (webdav) calendars are sometimes marked read-only on creation
- Bug 329486: (Lightning) Agenda view’s displayed times aren’t always in the correct timezone.
At this point, the MozStorage problems were fixed and when things tested nicely with the next set of nightly builds, we had Lightning 0.1RC1
It didn’t take long before we found at least one more bug that we wanted to fix before releasing the final version of Lightning 0.1. In the end, 2 bugs were fixed between RC1 and RC2.
- Bug 329647: (Lightning) Agenda view sorts events based on their time in Los Angeles, should work off local time.
- Bug 329800: (Lightning) Agenda view puts events starting at Midnight, and all day events, in the wrong day
And that brought us to the current state, Lightning 0.1RC2. At the time of this writing, there have yet to be any bugs filed that would stop RC2 from becoming the final Lightning 0.1. Again, immense thanks goes out to everyone who has helped us test and provided feedback concerning these release candidates.