Status update (27 Feb)

The following bugs have had fixes checked in since the last status update and we have made significant progress towards the
Lightning 0.1 and the Sunbird 0.3 alpha2 release.

  • Disable recurring todos until Bug 328197 is sorted out
  • Bug 300117: (Both) Recurring events are not visible on ‘until’ date
  • Bug 315051: (Both) Switch to storing alarms based on offsets from start/end time rather than as absolute times. Ensure that missed alarms are fired
  • Bug 320178: (Both) Need UI for editing single instance or all instances of recuring events
  • Bug 322859: (Both) Organizer is incorrectly converted to an attendee on ics roundtrip
  • Bug 323085: (Lightning) Add import/export functionality for lightning
  • Bug 323085: (Sunbird) Improve options/UI for Sunbird
  • Bug 325932: (Both) ‘Hide Completed Tasks’ button doesn’t work for tasks created with Sunbird 0.2
  • Bug 326074: (Both) Edit event via middle/right double click should not be possible
  • Bug 326077: (Both) cannot delete modified events from a series
  • Bug 326132: (Both) Start time of all-day events is set to odd times
  • Bug 327175: (Both) Define text color for selected event too (better legibility)
  • Bug 327840: (Both) Attendee participationStatus lost when cloning an event due to typo
  • Bug 327890: (Both) Serialize exceptions to ics calendars
  • Bug 327971: (Both) Fix for schema-checker failure blowing away database tables
  • Bug 328197: (Both) Fix a couple of thinkos which cause bad things to happen when dealing with recurring tasks
  • Bug 328504: (Both) Error parsing ics file with X-MOZ-LASTACK element due typo
  • Bug 328631: (Both) Position of the label ‘category’ inside New-event dialog is too high
  • Bug 328636: (Both) Editing event with reminder (15 or 30 min.) crashes Thunderbird (branch)

The Lightning 0.1 release blocker list
is down to only a few bugs and with the exception of Bug 323093
the remaining bugs are mostly in the build config or release preparation area. So we’re pretty confident, that we can release
Lightning 0.1 in the next two weeks, even though we won’t release Lightning 0.1 until tomorrow as dmose already
pointed out in the
developer newsgroup.

10 comments

  1. A lot of bugs are being fixed.. great to see lightning and sunbird moving forward.
    Will all the data-loss bugs be fixed for 0.1 ?
    it also looks like bug 323430 is fixed..
    nightly branch builds can be found here:
    http://ftp.mozilla.org/pub/mozilla.org/calendar/lightning/nightly/latest-mozilla1.8/

  2. My mirror still has files dated 26th (not working for me) unfortunately. Waiting :-)

  3. I’ve the same problem. the nightly 26/02/2006 (windows) doesn’t work for me too…

  4. I had the same problem with the nightly of the 26th.
    The nightly has now been updated (27th) but it is still not working for me (windows)!?

  5. The forum at http://forums.mozillazine.org/viewforum.php?f=46 is the better place to ask support question.

  6. How about the translations? Before releasing 0.1 Lightning – will you ask us localizers to update the files – is that needed at all at this time?

  7. Huzzah! Progress going fast.

  8. Guys,
    It’s great to see you have almost got 0.1 of this superb app ready, I already migrated from Corporate Outlook to Mozilla Thunderbird with Calendar, once the 0.1 of this is out I will be severely Happy.
    P.S the nightlies don’t work on 1.5, i suppose that’s because they’re still a bit buggy right? 0.1 will work with 1.5 ?
    Gary

  9. Stefan Sitter

    Gary: You find Lightning nightly builds for Thunderbird 1.5 here: http://ftp.mozilla.org/pub/mozilla.org/calendar/lightning/nightly/latest-mozilla1.8/. (This builds are meant for testers so backup your profile before using or test with a separate profile)

  10. I don’t know how to log a bug but I just downloaded the nightly build and it seems as though when you enter a new task where you set the alarm to custom and 0 minutes before, finalise/ok it then go back into edit it again… the alarm defaults back to 0 days before instead of minutes.
    FYI.