The Sunbird Project is a redesign of the Mozilla Calendar component. It is currently in Alpha.
Sunbird’s sister project at Mozilla is Lightning, a project to build a Thunderbird calendar extension.
Sunbird is designed to interact with other Mozilla projects via the Lightning extension.
There has been some trouble with an accidental SQLite database schema change I've backed out on monday (see bug 446303), which has forced people (which have updated to that specific nightly) to manually restore their storage.sdb.
I'd like to remind everybody that the nightly builds of Sunbird and Lightning are development versions that might break your profile and data. Even though the recent case didn't bring any dataloss (at least I am not aware of any) and a workaround is available, please take care and do backups before updating.
To prevent SQLite database schema trouble in the future, we've decided to require an additional second review on schema changes, and may add a bug keyword to tag those important changes.
I hope you understand...
We're getting nearer and nearer to our first 0.9 release candidate. With 34 bugs fixed in the last two weeks, many of them release blockers, we're now down to only 18 release blockers at the time of writing. 10 of those 18 bugs currently still need a patch, so if anyone of our readers wants to help out, now would be a great time.
On the localization front, 30 of our 33 are ready for the release (hopefully Macedonian, Slovenian and Turkish will still be able to make it), so we'll likely be in better shape l10n-wise than we were during the time of the 0.8 release.
For anyone interested, here are the 34 bugs fixed within in the last two weeks:
Many thanks go to all developers, contributors, localizers, testers, and supporters that make this possible.
The next test day will be held on Thursday, August 14th. This time we want to take a look at all localized Sunbird builds. Currently there are 33 languages available, and testing all of them is a huge amount of work. You can find the localized builds at http://ftp.mozilla.org/pub/mozilla.org/calendar/sunbird/nightly/latest-mozilla1.8-l10n/. The goal of our test day is to run as many Localization Litmus test cases as possible. Your feedback by editing the Test Plan for 0.9 is appreciated.
There are also many fixed bugs that need to be verified. You simply have to add a comment to the bug report stating what product, version and operating system you used while verifying the bug fixed.
Join us in the #calendar-qa IRC channel on Thursday. All the information on the testday is on our usual Test Day wiki page.
Hope to see you in #calendar-qa!
Andreas & Martin
Calendar QA Team
Sunbird and Lightning both have a feature called the "unifinder". It's the box at the top if you click the toolbar "Find Events". Next to the search text field you can select different time ranges to be scanned matching your search (or just present all matching the range if you leave it blank). The drop down box offers several time ranges, such as "All Events", "Today's Events", "Next 7 Days", ...
While the ranges look sensible, they cause me some headache, more specifically the unbounded ranges "All Events" and "All Future Events" w.r.t. infinite recurring events. If you select one of the unbounded ranges (e.g. "All Events"), the current implementation will only show the master items of recurring events, because there's no finite range to expand into. It shows the events in their condensed (unexpanded) form. While this approach misaligns the UI a bit (the other filters show recurring events in expanded form), it looks like a feasible way at first glance (modulo bugs around it). But there's yet a further problem with this approach: You could override´single occurrences of a recurring series, e.g. modify the start and end of an occurrence. Those are currently left out.
The latter and the inconsistent UI let me doubt that showing event series in condensed form is really what we want here, moreover because IMO showing expanded occurrences is far more intuitive. Solving the problem, I can imagine two solutions:
For the moment, until we have a good solution, I'd vote to remove the unbounded ranges.
I hope there are more options that we could consider, and would like to hear your feedback on this topic...
So I'm back from the Mozilla summit and hope to get out of my jet lag within the next few days. It was really a great adventure with bears, a power outage and a rockslide which got me first floatplane flight ever.
While many people seem to believe that Microsoft is behind all of this, I believe that this was all carefully planned out by Dan Portillo and John Lilly of MoCo :) My hat goes off to dan, who did a perfect job of organizing this whole event for over 400 people.
The summit was great in every aspect. I met lots of people, who I had only known online for years like Gary from the Rumbling Edge, Robert Kaiser (KaiRo) of SeaMonkey fame, Wayne Mery (Thunderbird QA), Axel Hecht (Pike), Mitchell Baker, the hopefully soon to be appointed MoFo Executive Director Mark Surman and many more who I can't possibly all name, because then this post would get a few pages longer.
The sessions were great (I went to most of the Calendar/Thunderbird related ones) and I even got to hold one session myself, where I could introduce myself to a lot of localizers in my new role as Thunderbird localization coordinator.
Besides the sessions, I also got the chance to talk with some people more in depth about some issues, most notably with Mitchell Baker, David Boswell and Mark Surman about sorting out the issues of getting the Calendar Project into the Mozilla Foundation directed giving program, the Mozilla Foundation vision and more ways of cooperating with the Mozilla Foundation and leveraging its assets to move the Calendar Project forward. We also did some product planning regarding the necessary steps for enabling Lightning in Thunderbird.
There's much more, that I could talk about, but I will just close this post by saying that this was a really great event, that many people will likely be talking about for years to come. Thanks Mozilla for organizing this!
Recently I was thinking about how we could show to people the progress in terms of activity, feature work and bug fixing that the Calendar Project has seen in the last few years. I came up with a number of bugzilla reports showing the number of bugs fixed per quarter since the inception of the Calendar Project.
I put all those numbers into a spreadsheet and created a graph from that and here it is:
While it's important to note that not all bugs are equal (A very complex thing like "Support device sync" would be one bug as would be something trivial as "Change window title from 'Edit event' to 'Open event'"), I think it still gives a good sense on the kind of increased activity that one could notice within the last few years in the Calendar project.
If anyone is wondering why we had such a huge drop of fixed bugs in Q2 2007, that was due to one of our key contributors being away for a few weeks in that time frame and the other developers waiting for him fixing a particular bug that was blocking the 0.5 release that was supposed to be released in that time frame.
Recently I was thinking about how we could show to people the progress in terms of activity, feature work and bugfixing that the Calendar Project has seen in the last few years. I came up with a number of bugzilla reports showing the number of bugs fixed per quarter since the inception of the Calendar Project.
I put all those numbers into a spreadsheet and created a graph from that and here it is:
While it's important to note that not all bugs are equal (Something like "Support device sync" and "Change window title from 'Edit event' to 'Open event'"), I think it still gives a good sense on the kind of increased activity that one could notice within the last few years in the Calendar project.
If anyone is wondering why we had such a huge drop of fixed bugs in Q2 2007, that was due to one of our key contributors being away for a few weeks in that timeframe and the other developers waiting for him fixing a particular bug that was blocking the 0.5 release that was supposed to be released in that timeframe.
As promised here is a new status update.
As you can see, the last 16 days have brought us a huge load of 45 bug fixes in anticipation of the upcoming 0.9 release. Unfortunately, due to the high amount of remaining blocking bugs (28 at the time of writing) we had to postpone the originally planned release date of 0.9 RC1 to a later date. I'll keep you posted on this.
Here's the list of all the 45 bug fixes:
Many thanks go to all developers, contributors, localizers, testers, and supporters that make this possible.
I'll be leaving today for the Mozilla summit in Whistler, Canada. Daniel, Philipp and Martin are also coming from the Calendar team as are hundreds of other key contributors from all major mozilla projects and products.
I hope to have some good discussions on the future of Mail & Calendar, localization and other issues that I've been pursuing. This will be a good time to finally meet in person many of the people that I've only been in contact with via newsgroups, mail and IRC.
You guys can also expect a new status update within the next few days. Until then...
After a short discussion at the QA chat last week, we decided that the next test day will be held on Thursday, July 24th. The main focus of this test day will be the Today Pane functionality (Berend added some minor features in bug 429687). We will also take a look at the new calendar view navigation (bug 444292), and try to find regressions.
There are also many fixed bugs that need to be verified. You simply have to add a comment to the bug report stating what product, version and operating system you used while verifying the bug fixed.
Join us in the #calendar-qa IRC channel on Thursday. All the information on the testday is on our usual Test Day wiki page.
Hope to see you in #calendar-qa!
Andreas
Calendar QA Team
Daniel landed some highly demanded iTIP/iMIP features today, and we want to put email-based scheduling (iTIP/iMIP support) to the acid test on our testday, tomorrow, Thursday, July 17th.
The landed patch allows the user to select an Email Identity for a calendar, which in turn is useful for accepting invitations so that the application can determine which identity to use when sending a reply. Also, calendar providers were given more control of how invitations are handled.
Join us in the #calendar-qa IRC channel tomorrow. All the information on the testday is on our usual Test Day wiki page.
Hope to see you in #calendar-qa!
mschroeder
Calendar QA Team
As discovered by SecuriTeam it's possible to discover the real name behind a Google mail addresings in web forums, mailing lists or newsgroups. It could also give spammers the ability to send you more targeted advertisements.
More details are in the relavnt SecuriTeam blog post. Since a lot of our users use Google Calendar, I thought I might pass this along.