05
Mar 10

How to solve incompatibility problems when upgrading to Thunderbird 3.0.3

Some of our users currently seem to experience problems with Lightning becoming incompatible when they update their Thunderbird installation to the 3.0.3 release.

The reason for this seems to lie in the fact that those users use a Lightning nightly build and update it on a daily basis with the Lightning Nightly Updater add-on or manually update to the latest available nightly build. But because we moved our Lightning nightly builds to only support the current Thunderbird 3.1 development builds, as reported earlier, this leads to the incompatibility.

The solution is simple though:
Just uninstall your current nightly build and install the Lightning 1.0 beta1 release. This release is identical to the latest available Lightning nightly builds for Thunderbird 3, but fully compatible with the Thunderbird 3 release. And to be on the safe side: Please backup your profile folder, before doing this!


04
Mar 10

Lightning users on Thunderbird are in the majority for the first time

Three weeks ago, I shared some usage statistics for Lightning with you.

One of the things that I looked at then was the adoption of Thunderbird among Lightning users. Back then Thunderbird 3 users were still lagging behind, but now I can report that on the last weekend, the ratio of Lightning users on Thunderbird 3 was higher than the ratio of Thunderbird 2 users for the first time. Here’s the graph showing the steady increase of Thunderbird 3 usage since November 25th in 2009, when the first release candidate for Thunderbird 3 was released.

As already noted in the earlier article, the ratio of Thunderbird 3 users is much higher on the weekends compared to the Thunderbird 2 users. But even during the workweek we’re catching up pretty fast, even faster than on the weekends.

Interested observers will notice that the graph in this post and the earlier graph differ slightly. The reason is that in the current chart I’ve also incorporated the numbers of pre-release versions, like 3.0 beta3 or 2.0.0.24pre.

And if someone is asking himself why I only list Thunderbird 3 and Thunderbird 2 ratios here, the answer is that all other versions, e.g. users of Thunderbird 3.1 nightly builds, Thunderbird 1.5 users, SeaMonkey users and people that installed Lightning into Firefox all taken together account for not more than 0.5% of our total active daily users.

I hope that you will find this as interesting as I do.


16
Feb 10

Whats going to happen in the next 6-8 weeks

As you may have noticed, not much has happened since the release of Lightning 1.0 beta 1. One reason for this is that I’ve had 8 Exams in the last three weeks, all of which needed quite an amount of preparation. I haven’t gotten grades for all of them yet, but those I received so far were pretty good.

Now that all of this is through, I have a lot more time for Calendar. I will be enjoying semester vacation until April, which means I can catch up on all the calendar work I have missed.

I’d like to give you a short overview of what my next steps are, so you know what to expect.

  • Planning for 1.0 final. We need to firm our goals for Lightning 1.0 final. I’m going to define some toplevel goals I think would be good for the final and go through bugzilla to identify the most important bugs to fit those goals. Afterwards, I will discuss these goals with the Calendar Team more closely.
  • Reviews. My review queue has filled up and is now at 35 requests. I have already tagged each patch with its length and will now be taking care of these one by one. I can’t dump in all patches at once so it might take a while until they are all in the tree, but I’ll be pushing more than one a day if the patches come from different areas and the reviews are done.
  • Improve Localization Infrastructure. This step is long overdue, we wanted to have this working before 1.0b1 already. It would be a great advantage for Localizers if they could see how their changes affect Lightning builds. To make this happen, I need to work on the buildbot code so it builds localized Lightning packages automatically for the nightly builds.
  • Patches. I do have a few patches in the works that need more elaborate testing and also some coding, I would like to complete these soon, as long as they make sense for the next version.
  • Planning for 1.0b2. Depending on what the outcome of the 1.0 final planning is (i.e if we think the next version should still be a beta), we will also spend some time planning for 1.0b2. This includes top level goals and also some driving work to get the blocking list into shape.

This should keep me busy for a while, I’ll post again when I have new goals to share. Let me know what you think!

Philipp


11
Feb 10

Taking a closer look at Lightning download numbers

It’s now been thirty days since the release of Lightning 1.0 beta1 and so far it’s been a blast.

Daily Lightning downloads

I regularly take a look at our download numbers and wanted to share some recent developments with you. First of all, let’s take a look at our daily download numbers since 2009-01-01:

What’s easy to see here is the huge reception that Lightning has gotten from our users since the 1.0 beta1 release. You can see it with the small spike in mid-December 2009 (announcement of the 1.0 beta1 release candidate) and the large spike 30 days ago, that marks the final release of 1.0 beta1. The corresponding moving averages show even better how much our daily download numbers have increased. To give some hard numbers: We’ve gotten more than 310,000 unique downloads within the last 30 days. That’s 50% more than we’ve gotten at any time since we measure our daily download numbers (which we do since September 2007).

I should add two things here:

  1. The regular downward spikes are the weekends and holidays, which always show much smaller numbers.
  2. The numbers only contain actual downloads. They do not contain add-on updates.

Lightning active daily users (ADU)

Another good indicator are our number of active daily users, which we’ve been measuring since late May 2009 and which can be tracked on a daily basis at addon.mozilla.org.

Again, it’s easy to see the steady upward trend that started around late August 2009. The downward spikes on every weekend are also easy to see, as are our low numbers around the year-end holidays, which seem to indicate, that Lightning is mostly used for business purposes and not so much for private use.

Thunderbird 3 adoption among Lightning users

Lastly, let’s take a look at what our users are actually using. How many people have already updated to Thunderbird 3?

The chart starts in late November with the first release candidate of Thunderbird 3 and it’s easy to see the first large increase on the day of the Thunderbird 3.0 release (December 08 2009). The release date of Lightning 1.0 beta1 (January 12 2010) is harder to spot here, but the uptake is still noticeable. What is pretty clear is the steady increase of Thunderbird 3 users and the corresponding decline of users of Thunderbird 2. Interestingly, the ratio of Thunderbird 3 users is much higher on the weekends compared to the Thunderbird 2 users. One possible explanation would be, that normal users , which also use Lightning during the weekend, are faster with upgrading than business users, which only use Lightning during the work week.

One interesting additional fact, that cannot be gleamed form those charts is the fact that Lightning users seem to be much more eager to update to Thunderbird 3, than Thunderbird users which do not use Lightning.
The last available numbers speak of a total of 6 million active daily users of Thunderbird during the week of which 1.4 million are already using Thunderbird 3. That would put the ratio of Lightning users at 15.5% overall (calculated with a value of 930,000 active daily Lightning users during the work week). However if you take a closer look at the various versions of Thunderbird, you can see that the ratio of Lightning users among Thunderbird 3 users is much higher (22.8%), while it is much lower among users of earlier Thunderbird versions (11.4%).

I’d be interested in your thoughts on this.


08
Feb 10

[February 08, 2010] Lightning Status Update

Now that we’re moving full-steam towards the Lightning 1.0 beta2 release, it’s also time to make clean slate and show you in terms of fixed bugs, what has happened since the last status update back in late November 2009.

Overall we have fixed an impressive 55 bugs since then, keeping in mind the whole release process hassle, the holidays and Philipp’s exam schedule. Here’s the complete list of fixed bugs:

  • Bug 313822: Make Lightning work on SeaMonkey
  • Bug 357332: Holidays in Chile for 2010
  • Bug 364487: Argentina Holidays 2008-2009
  • Bug 376139: Sri Lanka Holiday 2010
  • Bug 397180: South African Holidays 2010
  • Bug 432440: Israel Holidays 2010
  • Bug 472466: No small icons in edit event/task dialog available
  • Bug 489882: Building with “NECKO_DISK_CACHE=” fails with unresolved external symbol
  • Bug 500399: Event Dialog: Help Menu is uselesss and could be removed
  • Bug 509100: Holiday file for Namibia
  • Bug 511193: [Mozmill] Recursion tests
  • Bug 518610: Tasks no longer work in TB3/Lightning with Kerio Mailserver
  • Bug 524574: Polish holiday 2009-2020
  • Bug 528676: e-mail list not updated when using next/prev button in New Calendar wizard
  • Bug 529810: Views borked using wcap: dayHeaderBox.mItemBoxes is null
  • Bug 529853: Creation of local calendar fails (DB Error no such column: recurrence_id_tz)
  • Bug 530096: Tracking bug for Sunbird/Lightning 1.0b1 release
  • Bug 530097: Create release notes for Lightning/Sunbird 1.0b1
  • Bug 530100: Bump version numbers for 1.0b1 release
  • Bug 530165: [Mozmill] Timezone test
  • Bug 530842: Upgrade Sunbird/Lightning 0.9 to 1.0pre fails
  • Bug 531028: Linux: Delete Task button in Task view is missing its icon
  • Bug 531418: Allow building lightning with all locales at once
  • Bug 531685: Build problems on linux and win32 due to insufficient disk space
  • Bug 531699: Spanish Holidays 2007-2010
  • Bug 532656: Fix Sunbird official branding on Mac.
  • Bug 533070: Sunbird nightly builds fail with |No rule to make target
  • Bug 533089: Malta Calendar 2010
  • Bug 533259: Sunbird website does not validate to its doctype
  • Bug 533324: Finnish Holidays 2010
  • Bug 533329: [Mozmill] Verify that Calendar is working properly with UTF-8 characters
  • Bug 533458: Fix mac and windows trunk builds
  • Bug 533466: calendar-multiget REPORT should not specify the calendar collection URL
  • Bug 533498: Build config changes for Cocoa Printing
  • Bug 533713: gdata-provider.xpi should support SeaMonkey 2
  • Bug 533747: Mention required version of Thunderbird in system requirements of Lightning
  • Bug 533943: CalDav access to my calendar doesn’t work on RC2, lightning 1.0, using CGP
  • Bug 534969: Add sq to calendar/locales/all-locales
  • Bug 535379: Create more l10n.ini files to builds against 1.9.1 and central
  • Bug 535574: [Mozmill] Writing to a local ICS calendar
  • Bug 535812: [Mozmill] Event with no changes shouldn’t prompt to save
  • Bug 536185: Update calendar/ copyright dates to 2010
  • Bug 536189: Wrong Lightning version in install.rdf
  • Bug 536354: getItem doesn’t set calendar for items
  • Bug 536525: Turkey holidays for 2010
  • Bug 537066: Scrape dead bits out of credits.xhtml
  • Bug 537470: Russian Holidays 2010 and onward
  • Bug 537628: Building localized Sunbird l10n nightly builds fail since 02-Dec-2009
  • Bug 537885: Add Arabic (ar) to Calendar builds
  • Bug 538170: Mac trunk builds failing running merge-installrdf.py
  • Bug 538439: static Sunbird builds from comm-central/mozilla-central fail
  • Bug 538576: Singapore Public Holiday 2010
  • Bug 539681: Puerto Rico Holidays
  • Bug 539943: Set up builders for Lightning 1.0b2pre for Thunderbird 3.1
  • Bug 543359: Adjust Lightning version and required Thunderbird version

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


07
Feb 10

Lightning builds move towards supporting Thunderbird 3.1

Some people have already noticed that we no longer release nightly builds that support Thunderbird 3.0 and SeaMonkey 2.0. As of January 31st, our nightly builds will no longer live in the latest-comm-1.9.1 folder, but in the latest-comm-1.9.2 directory.

The main difference between the 1.9.1 builds and the 1.9.2 builds is, that the latter will only support nightly builds of the Thunderbird 3.1 and the SeaMonkey 2.1 development branch. This also means that our next Lightning release (1.0 beta2) will not support Thunderbird 3.0.x and SeaMonkey 2.0.x and users of those releases will have to update to be able to get the latest Lightning release then. For now, users that want to test the latest Lightning fixes should either download Lanikai 3.1 alpha1 or a recent nightly build of Thunderbird (also called Shredder) or SeaMonkey.

The reason for this decision is (again) one of (developer) resources. Currently the following development areas/branches are available to us:

  • The comm-1.9.1 branch, where development for Thunderbird 3.0 and SeaMonkey 2.0 took place.
  • The Gecko 1.9.2 branch (home of Firefox 3.6) that in combination with the (soon to be created comm-1.9.2 branch) will be the basis for Thunderbird 3.1, which is currently scheduled for a release in April 2010.
  • The so called trunk, on which the release after Thunderbird 3.1 will be developed. The SeaMonkey folks are targeting the trunk for their 2.1 release.

With our current resource situation we are not able to fully support all three areas/branches. We have therefore decided to only fully support the Gecko 1.9.2 branch and give a somewhat limited support to the trunk. Those of you who want to follow our work are encouraged to download the Lightning Nightly Updater add-on, which should make updating Lightning much easier for you.

Thanks for staying with us.


21
Jan 10

Lightning 1.0 beta1 users – Please upgrade to Thunderbird 3.0.1

Yesterday, Mozilla Messaging released Thunderbird 3.0.1, its first security, stability and maintenance release after the initial Thunderbird 3 release.

While it’s always a good idea to quickly update to such a maintenance release for security reasons, this release also contains one important fix for Lightning users, who like to use Lightning in combination with other popular Thunderbird extensions (Enigmail, Quick Folders, Buttons!, etc.). Without this fix, some of our users were affected by bug 398702, which caused the File, Edit and View menus to disappear.

This bug has now been fixed in Thunderbird 3.0.1, which is why we recommend this update to all our users of Lightning 1.0 beta1.


15
Jan 10

Statement on the recent Lightning 1.0 beta1 release

There seems to be some doubt in our community regarding the status of the recent Lightning 1.0 beta1 release in our release hierarchy.

So let me unequivocally state for the entire Calendar developers team:

  • We (the Calendar developers) consider Lightning 1.0 beta to be the best Lightning release, that has been released to the public so far.
  • We consider Lightning 1.0 beta1 to be the stable release built for users of Thunderbird 3 and SeaMonkey 2.
  • It contains numerous bugfixes and improvements (nearly 500) over the 16-month-old 0.9 release, that improve the add-on’s stability, performance and memory consumption.
  • We encourage everyone to update to this release from Lightning 0.9 or earlier Lightning releases.
  • We are not planning to release any updates to Lightning 0.9 users, that want to remain on Thunderbird 2. Thunderbird 3 is the future as far as we are concerned.

13
Jan 10

More news on the Lightning 1.0 beta1 update

The two most asked questions regarding the new Lightning release so far were:

  • Where is the x86-64 build for Linux?
  • Is there also an update available of the Provider for Google Calendar (GDATA) add-on?

I’m happy to report that both issues could be resolved successfully:

Our thanks go to the Calendar lead developer, Philipp Kewisch, who provided the x86-64 build and who maintains the GDATA add-on. Great work, Philipp!


12
Jan 10

Lightning 1.0 beta1 now available for download

The Calendar Project is proud to report, that (finally) the 1.0 beta1 release of Lightning has been completed and is now available via AMO.

Nearly 16 months after the 0.9, this release is more than overdue and we’re more than happy to get the nearly 500 bugfixes and improvements into the hands of our users. Notable improvements of this release are:

  • Seamless integration into the new Thunderbird 3.0 user interface
  • The different modes (calendar view, task view) are now displayed in tabs
  • Lightning now supports SeaMonkey 2.0 as a host application
  • You can now define multiple alarms for a single event
  • CalDAV support and interoperability with various CalDAV servers have been improved
  • The application stability, performance and memory consumption have been improved
  • Estonian, Frisian, Galician, Hebrew, Indonesian, Punjabi, Sinhala, Tamil, Turkish and Vietnamese were added as new languages. Unfortunately no builds in Traditional Chinese, Slovenian, Swedish or Ukrainian are available for 1.0 beta1

Lightning 1.0 beta1 is available for Windows, Mac OS X (universal builds) and Linux in 37 different languages including English. Please read the release notes for Lightning 1.0 beta1 before downloading.

Thank you again to all our developers, contributors, localizers, testers, and supporters. We would not be able to do this without your assistance!