20
Jun 10

Lightning 1.0 Beta 2 Release Candidate 3 is available

This new release candidate contains fixes for a few locales, no further code changes. Since the Thunderbird 3.1 release is scheduled for this week, I assume this will be the final release candidate.

Candidate builds for Lightning 1.0 beta2 in 33 languages are available as of now for:

A corresponding build of the Provider for Google Calendar is also available at those locations and will be uploaded to addons.mozilla.org once the release cycle completes.

For install instructions, please see one of the earlier blog posts.

Please tell us what you think of these candidate builds and file bugs in Bugzilla as you go. The release is near, and we are glad we can finally concentrate on the next one!


17
Jun 10

Lightning 1.0 Beta 2 and Compatibility

A few people have asked me different compatibility questions around Lightning 1.0b2. I’d like to take a moment and tell you about what applications Lightning 1.0b2 will support.

What version(s) of Thunderbird will Lightning 1.0b2 support?
This version of Lightning will only support Thunderbird 3.1. To go a bit more into the technical details, Lightning 1.0b2 and Thunderbird 3.1 use the Mozilla Platform version 1.9.2. The previous versions (Lightning 1.0b1 / Thunderbird 3.0.x) use the Mozilla Platform version 1.9.1. Therefore we cannot provide a version of Lightning that is compatible with Thunderbird 3.0.x

Will Lightning 1.0b2 support Seamonkey?
As you can see in this blog post, Seamonkey does not support the Mozilla Platform version 1.9.2. Therefore, Lightning 1.0b2 cannot support Seamonkey 2.0 or 2.1. Note however, the next version of Lightning will most likely use the Mozilla 1.9.3 Platform, which means the next release (due in about 4 months) will be compatible with Seamonkey 2.1. Until then you can still use Lightning 1.0b1 together with Seamonkey 2.0.x.

Which version of the Provider for Google Calendar should I use?
Together with Lightning 1.0b2, I will release a new version of the Provider for Google Calendar. This version will be called 0.7 and will be available on addons.mozilla.org together with Lightning.

Why don’t you use the latest Mozilla platform, verion 1.9.3?
The 1.9.3 platform contains the newest features and bugfixes to date, but this also means that some Mozilla components we use, as well as some UI features, have changed and require us to adapt our code. Changes in the platform can happen every day, which means it doesn’t make sense to rely on it for a release. Just imagine something big changes between now and next week: this would postpone the release indefinitely, which is obviously bad. Another factor is that the newer platform has binary components that have a different interface. If we build Lightning with Mozilla 1.9.3, it won’t be compatible with a Thunderbird on the Mozilla 1.9.2 platform. It makes sense to use the same Mozilla platform version that Thunderbird does, this causes the least amount of headaches.

Why are you releasing betas, and not 1.0 final?
There is a certain level of stability that people expect from such a major release such as 1.0. We have decided on a certain set of bugs that we think should be fixed before 1.0 final is released. Back when we released 1.0b1, we had a few possibilities on what we should name it. There was 0.10 (as in 0.8, 0.9, 0.10, …), but people could think this is similarly mature as 0.1 was. There was 0.9.5, but we wanted to make clear that the Mozilla platform used has a different minor version (1.8.x vs 1.9.x). So we ended up with 1.0b1. Now we have no other choice than to continue with betas until we’ve fixed all the bugs we think make sense for 1.0 final.

I hope this gives a bit of insight, if you have any further questions, please comment!


15
Jun 10

Lightning 1.0 Beta 2 Release Candidate 2 is available

With some delay, we are happy to announce Lightning 1.0b2 release candidate 2. With this release we’ve mainly fixed bug bug 570464, but also made sure we were using the right localization files.

Please re-test if Lightning works in your language! Back with rc1, I accidentally used the newest version of the localization files, but not the version that the localizers suggested. I did notice some further change to the localization files, so it would be great if you could double check.

Candidate builds for Lightning 1.0 beta2 in 33 languages are available as of now for:

A corresponding build of the Provider for Google Calendar is also available at those locations.

Note you will need Thunderbird 3.1 (or a release candidate thereof) to try it out. You are encouraged to back up your profile before upgrading. To install these builds in Thunderbird 3.1, please follow these steps:

  1. Download the build for your operating system to a folder on your hard disk.
    NOTE:Please make sure, that you right-click on the links above and choose “Save Link as…”. Otherwise Firefox will try to install Lightning and you will get an error message like “Lightning 1.0b2 could not be installed because it is not compatible with Firefox.”
  2. Open Thunderbird, then open its add-on manager via Tools –> Add-ons (or the corresponding entry in your language)
  3. Click on the “Install…” button on the lower left and navigate for the lightning.xpi file that you just downloaded.
  4. Restart Thunderbird after the add-on installation has been performed. Voila!

We will be releasing the final version of Lightning together with Thunderbird 3.1. There is not much time left before this release, so I encourage you to do the testing rather sooner than later.

Please tell us what you think of these candidate builds and file bugs in Bugzilla as you go. We are really looking forward to this release, I hope you are too!


07
Jun 10

Lightning 1.0 Beta 2 will have a second release candidate

Due to (at least) bug 570394 and bug 570464, we need to respin for rc2. This will happen quite soon (in the next few days), since we need to keep up with the release dates for Thunderbird 3.1.

If you are a localizer and would like to do any further changes for 1.0b2, please file a bug and contact me as soon as possible.


03
Jun 10

Lightning 1.0 Beta 2 Release Candidate 1 is available

This time around, we had a lot less trouble then last time when preparing 1.0b2 release candidate 1. The most trouble this time was again release automation. We managed to work around the issues by producing manual builds on the same machines as our usual releases are built on.

Candidate builds for Lightning 1.0 beta2 in 32 languages are available as of now for:

A corresponding build of the Provider for Google Calendar is also available at those locations.

Note you will need Thunderbird 3.1 (or a release candidate thereof) to try it out. You are encouraged to back up your profile before upgrading. To install these builds in Thunderbird 3.1, please follow these steps:

  1. Download the build for your operating system to a folder on your hard disk.
    NOTE:Please make sure, that you right-click on the links above and choose “Save Link as…”. Otherwise Firefox will try to install Lightning and you will get an error message like “Lightning 1.0b2 could not be installed because it is not compatible with Firefox.”
  2. Open Thunderbird, then open its add-on manager via Tools –> Add-ons (or the corresponding entry in your language)
  3. Click on the “Install…” button on the lower left and navigate for the lightning.xpi file that you just downloaded.
  4. Restart Thunderbird after the add-on installation has been performed. Voila!

The candidate builds will be available for testing for up to 2 weeks. We want to release the final Lightning 1.0b2 together with Thunderbird 3.1, so we may choose to shorten this period by a few days.

Please tell us what you think of these candidate builds and file bugs in Bugzilla as you go. Thank you very much for your support, we couldn’t do it without you!

Update: Windows link fixed, thanks for the note!


20
May 10

[Reminder] Localization sign-off deadline for Lightning 1.0 beta2 is on May 24

As announced nine days ago, the sign-off deadline for Lightning 1.0 beta2, the Lightning release that will accompany Thunderbird 3.1 is on May 24th at 23:59 pacific time.

Right now the picture looks like this:

  • 22 locales have already signed-off
  • 7 locales are green on the dashboard but have not yet signed off for their locale
  • 1 locale is orange on the dashboard indicating that some obsolete strings still need to be removed or commented out
  • Of the remaining 14 locales, many have only a limited amount of missing strings to catch-up. So it would be great if those locales could still join us

I will contact every locale that has not yet signed off their locale individually as well, so that everyone is aware of the current status.


11
May 10

@Localizers: Please sign-in for Lightning 1.0 beta2

As announced by Philipp two days ago the strings for the next Lightning release (1.0 beta2) have been frozen and you can now start to sign-in for this release.

We will be accepting sign-in requests until May 24 @ 23:59 pacific day time, so you have a little less than two weeks time to get your
locale in shape.

Lightning 1.0 beta2 localizations will be taken from the l10n-1.9.2 repositories, so please work from there.

If you have any questions, feel free to ask them in the mozilla l10n newsgroup or send me an e-mail.


08
May 10

String Freeze for Lightning 1.0b2 Release Today

I want to make those of you, who are actively translating Lightning aware, that we are now ready to freeze our strings for the approaching 1.0b2 release.

After the string freeze we are currently planning for two and a half additional weeks before we try to release our first release candidate on May 25th. We would really appreciate it if you could have your locales in shape for the first RC, as I do hope we will only need one release candidate. Please also note that we have to stay in sync with the Thunderbird schedule, so we might have to prepone our rc1 release to an earlier date.

That gives you 2-3 weeks to get your localizations in shape.

The 1.0b2 release will come from the comm-1.9.2 release branch, which means you should commit your work to the l10n-mozilla-1.9.2 repositories. If any of you will not be able to keep his or her locale updated for the 1.0b2 release, please let me know beforehand.

I am aware that we still don’t have bug 346278 fixed, I am really sorry this is still the case. If rc1 is released and you notice any localization problems, please do let me know as quickly as possible so I can coordinate a second release candidate. I do hope to fix this bug in the next two weeks though!

Please let Simon Paquet or me know if any of you wants to join us for 1.0b2.

If you have any questions, please do not hesitate to ask them here

Thanks,
Philipp

Update: It seems the calendar10x dashboard is not correctly updated. Please use the latest version of the dashboard to find out how many strings are missing!


22
Mar 10

[March 22, 2010] Lightning Status Update

As we’re moving closer towards our next release, Lightning 1.0 beta2, it’s time to talk more about our recent accomplishments and bugfixes. We’ve been pretty active in the last six weeks and over 40 bugfixes have made it into our code repository.

Overall we have fixed an impressive 43 bugs since February 8. Here’s the complete list of fixed bugs:

  • Bug 349996: Multiselection should be enabled to remove more than one category
  • Bug 351321: Italic and bold font for high and low priority
  • Bug 359016: JS error ‘this.currentItem has no properties’ in calItemBase propertyEnumerator
  • Bug 392737: Event dialog: No ‘save and close’ function in the new event file menu
  • Bug 395287: Event dialog: Cannot enable timezone option for ending time
  • Bug 405439: Recurring task -> repeating rule shows wrong start/end time
  • Bug 413296: Leaking object on window-close
  • Bug 416614: Doesn’t show completely an alarm when need to slide to select it
  • Bug 455232: Query for supported-calendar-component-set in case servers don’t support tasks/events
  • Bug 460030: Get rid of resize handler, use flex to draw view columns
  • Bug 465317: Today and Navigation Buttons need to be polished
  • Bug 476227: Drop shadow for multiday events has incorrect length
  • Bug 490169: Should be an easily-accessible option to fire an alarm “on time”
  • Bug 490303: Invites aren’t sent when using Sun Calendar Server and the meeting arranger is wrong
  • Bug 491254: Some languages need weekdays in plural form for some sentences in Recurrence Summary
  • Bug 498690: Support for webdav-sync spec
  • Bug 500283: Keyset in event-edit-dialog should be localizable
  • Bug 510930: Titlebar text is wrong when switch between Month/Multiweek
  • Bug 515643: Lightning messes up Thunderbird’s File->New submenu
  • Bug 519225: Shared calendar still shows events deleted by other calendar participants
  • Bug 525430: Task view doesn’t show the attachments for selected tasks
  • Bug 529813: Invite Attendees dialog: icons are messed up in case of missing participation role
  • Bug 533414: Drag shadow of events that span multiple days, doesn’t show the position of the whole event
  • Bug 534045: Invite Attendees dialog: icons are messed up in case of participation role NON-PARTICIPANT
  • Bug 538589: Remove button removes the reminder following the selected one in the list
  • Bug 538873: CalDAV: Cannot Delete Event
  • Bug 539512: Font Color changes with Persona’s Skins
  • Bug 539681: Puerto Rico Holidays
  • Bug 542210: Lightning does not update Sun Calendar
  • Bug 543698: Moved occurrences of repeating all-day events are displayed on new and original date
  • Bug 543744: Add calendar name to event tooltip information
  • Bug 544082: Update failing Mozmill tests
  • Bug 544682: Months should be viewed with different color to avoid confusion
  • Bug 544842: Nothing appears as “checked” when submenus “Progress” & “Priority” are opened
  • Bug 544858: Adjust Lightning version for GData provider on mozilla-1.9.2/mozilla-central
  • Bug 546300: Octal Numeric Constants are deprecated
  • Bug 546943: Don’t display drop shadows when dragging back to original date
  • Bug 550291: AsyncPromptAuth method is not implemented in calAuthUtils.jsm
  • Bug 550789: Update links for Lightning nightly builds
  • Bug 551147: Remove obsolete lightning/nightly/latest-comm-1.9.1 folder from ftp server
  • Bug 551231: Make xpcshell-based unit tests pass in JavaScript strict mode
  • Bug 552042: Calendar registry not written after creating/deleting calendar
  • Bug 552303: Errors while threading disabled

As always, our thanks go to all developers, contributors, localizers, testers, and supporters that have made this possible.


19
Mar 10

Reducing the Calendar bug count

We (mostly our lead developer Philipp) have done some heavy lifting with our bug database in recent days. During the last month, we waded through hundreds of bug reports (some of those being several years old) to see whether those bugs had been fixed by all the work that we’ve put into Lightning 1.0 beta1.

The result of this exercise was a reduction of our total open bug count by nearly 18% or in absolute terms, we’ve reduced the number of open bugs by 276 from 1552 to 1276. This chart illustrates our total open bug count from the start of 2010 until mid-March:

It’s important to note that not every bug in our database is a real program error. Our bug list also contains lot of enhancement request, project management issues and enhancement requests. Basically everything that comes up in our project that needs to be tracked somehow is entered in our bug database, so that it can be easily tracked.