Lightning 2.6 is going to be the release you are stuck with for about 42 weeks, so its vitally important that this one is tested thoroughly. All features are important to test, as not only Lightning code has changed, but also the Mozilla Platform behind it.
Get the Thunderbird 24 beta on the Thunderbird betas page.
Get Lightning 2.6b1 on addons.mozilla.org:
If you find an issue, please file a bug at bugzilla.mozilla.org, product Calendar. Search for an existing bug first. If you come across any major bugs (not missing features), a comment is fine too.
Thank you for your support!
I have put together a survey with a few questions on how you manage your tasks. Not only will it help me with my final thesis, it will also help me better understand how users manage their tasks.
Why it this important? The current tasks UI in Lightning is mostly a direct implementation of the technical spec. This might work for simple needs, but its far from effective for completing your tasks.
I have come up with a system that caters my needs, but as the goal is for lots of users with different needs to be able to use the system without frustration, I need to ask you a few questions.
The survey is not limited to Lightning users, everyone who has at least one task on his or her list should take a look. It should only take a few minutes to complete and most questions are multiple choice.
You can find the survey here: http://bit.ly/1cJHjaa. I will analyze the results on August 20th, so don’t forget to do this soon!
Please share, RT this tweet and tell your friends. Bonus points for finding someone who you know handles tasks quite different than you do.
Thanks in Advance,
As you may have noticed if you are using the beta versions, there have been a few localization problems in the past. This is not the localizers fault, but rather a problem with our build infrastructure.
I have been working on moving the Lightning builds from their own build machines to building together with Thunderbird. This doesn’t mean that Lightning will be pre-installed with Thunderbird, it just saves time while building since I don’t have to maintain a separate set of build machines.
Unfortunately, since Lightning is just piggybacking the Thunderbird build targets, this causes a dilemma for the localized builds. Before the localization process begins, the language files are downloaded from the mercurial server and updated to the specific version which was signed-off by a Thunderbird localizer. As Lightning can only hook into the build process itself, there is no previous step to update the language files to the version which was signed-off by the Lightning localizers. Adding this step is non-trivial.
In some cases it will magically work, if the Thunderbird localizer signed off a later version than the Lightning localizer, because the Lightning changes will then be contained too. Right now I don’t have a good solution other than to ask localizers to sign off on the Thunderbird dashboard. I’m trying to figure out some alternatives, in the worst case I will have to do the language repackaging manually for Thunderbird 24 / Lightning 2.6.
If you have some experience with Mozilla’s release engineering and have an idea how to solve this, I’m happy to hear it!
Just a quick note: Due to a slight packaging glitch, the Linux Lightning builds for 2.5b1 were broken. I have just uploaded 2.5b2 to addons.mozilla.org, you can get it in the “Development Channel” box or from the Other Versions page.
Its been quite a long time, but now I am happy to announce that localized nightly builds have returned. The main intent for these builds are to help localizers check if their language changes are correct, but of course anyone can use them.
You can get the builds for the comm-aurora branch or when the network outage is solved then also for the comm-central branch. There is one file per locale.
These builds are just in time for the major release of Lightning 2.6 which will be compatible with the Thunderbird 24 release. After the upcoming merge on June 24th, Lightning 2.6 will be on comm-aurora. If you are a localizer, please take the time to make sure your translations are accurate and ready for the release. If you are a user you can do the same, please report bugs in translation to the Mozilla Localizations product.
Thunderbird and Lightning/calendar bugday³
Hello Thunderbird and Lightning/Calendar enthusiasts. We need your help! Help us to make the next “big release” of Thunderbird, Thunderbird 24, the best release ever.
On June 12 skilled help will be available via online chat to assist you, for as little or as long as you like, in doing the following:
- Help other users by checking their bug reports to see if you can reproduce the behavior of their reported problem
- Get advice about your own bug report
- Help users in the support forum to see if a user’s problem needs a bug report
No coding or special skills are required. And you don’t need to be an expert or long term user of Thunderbird or Lightning. You simply need to be using Thunderbird to help other Thunderbird users. Or a a user of Lightning to help with calendar issue.
Just a little bit of your time will contribute to making Thunderbird and/or Lightning better for yourself and for others. Please see the details at https://wiki.mozilla.org/Thunderbird:QA_TestDay:2013-06-12
We look forward to having your help , and seeing you online in the chat area.
The Thunderbird QA Team
Since the last big release is a while back, I thought I’d let everyone know that the current Lightning 2.6 nightly builds on comm-central will become the release compatible with Thunderbird 24, the next big Thunderbird release.
What this means for localizers
When the current 6 weeks cycle ends, the code will merge down to comm-aurora as usual. At this moment you should be preparing your translations and signing off. There is no process change, you will still have time until the beta, but especially if you have a lot of untranslated strings you might want to start early. While the intermediate beta releases have not been so important, missing the deadline this time means up to 42 weeks of Lightning without your language.
What this means for developers
Have a patch you are working on? A nice new feature? Better get it in review soon, otherwise we might have to postpone it. Especially so if it contains string changes, additions or removals. Again, postponing means at least 42 weeks before its in the final release.
What this means for users
It is vitally important that you test the Lightning builds we offer. Given we haven’t had final releases in a while more regressions might have snuck in and its better we find them early. It would be super helpful if you could test the nightly builds, but if you want a little more safety, there is a test week in progress for Thunderbird and the current Lightning beta. You are of course encouraged to install the beta builds at any time. I personally use them for my production calendars.
While Thunderbird is having a test week, we’ve released the version that goes with it 2.4b1.
We are interested in catching regressions with regards to : Alarms, CalDAV Servers and Email Invitations.
The beta is on AMO now, I think the most user friendly link is https://addons.mozilla.org/en-US/thunderbird/addon/lightning/versions/?page=1#version-2.4b1.
Hello Folks. If you have been using Lightning 2.3b1 with a localized version of Thunderbird, you probably had troubles with undefined entities. This happened due to a glitch with the Mozilla localization dashboard, the wrong changeset was used.
I have just uploaded Lightning 2.3b2, which should fix the issue. As always, you can download beta versions from the addons.mozilla.org site in the “Developer Channel” box. If you have previously installed a beta, you should get the update via automatic updates.
We are happy to announce that a Release Candidate for Lightning version 1.9.1 is now available for testing here. For those using linux, please use the build in the linux/ folder rather than the platform-specific folders. Windows users can find their builds in the “unsigned” folder.
This version fixes an issue that prevents some events from being modified and some reminders from being dismissed in CalDAV calendars with Offline Support enabled – those affected are encouraged to test this build. If you have seen an error message with “this.mItemInfoCache[aNewItem.id] is undefined”, this is you! Be sure to reset your cache, by unchecking the “Offline Support” checkbox, restarting, then checking it again.
The full list of changes in this version can be found here.
It is really important that you test this pre-release, as it will become the next release for Thunderbird 17. There is no additional beta phase, this is it! If you are using Thunderbird 17, please give it a try and let us know if you encounter any errors.