Calendar Weblog

• Basque
• Belgium (Dutch)
• Chile
• Greece
• Kazakhstan
• Lebanon
• Malta
• Namibia
• Puerto Rico
• Singapore (Submitted, but not reviewed yet.)
• Sri Lanka
• Switzerland
• Turkey (Submitted, but not reviewed yet.)

• Click here and download the current version of the holiday calendar in your locale.
• Import the calendar into Lightning/Sunbird.
• Edit the Dates and/or add new Events/Holidays for at least the next 2 years.
• Export the calendar; switch to calendar mode and choose "File > Export Calendar". Then save the calendar file to a place that you can remember, e.g. your desktop.



• Go here and log-in with your Bugzilla credentials
• File a bug in the Calendar component, Website category. Describe, which locale you're adding a calendar file for and tell us what years your file covers.
• Attach your updated holiday calendar file to the bug (you created this in step 1)

Posted by Jan Bambach at 2:28 AM | Permalink | Comments (7)

If you have been using Lightning 1.0b3pre nightlies, you've been missing out on a number of fixed bugs and new features. This is because we've been concentrating on making Lightning work with trunk (the newest comm-central/mozilla-central code).

Although not finally decided, the next Thunderbird version is likely to be from the more stable comm-1.9.2/mozilla-1.9.2 branch. Therefore we have now backported all relevant patches to the comm-1.9.2 branch, giving you the chance to see what the next version will be like. If you are wondering why this hasn't happened before, it is important that bugs are fixed on trunk first. Otherwise it may happen that a future version loses features and bugfixes a previous release contained, due to problems while porting the code.

The Calendar Team would really appreciate if you could give this nightly a spin, especially if you are maybe using your own calendar server, or maybe one that is not so common. The earlier you test this version, the more likely it is that the 1.0b3 release will not contain bugs that make it unusable for you.

If you haven't yet downloaded Lightning 1.0b3pre, make sure you have a copy of Thunderbird 3.1 and get Lightning here. If you encounter any bugs be sure to search first. If you can't find a matching report then file a new one. Please also note which version of Thunderbird/Lightning you are using.

Note: The list of bugs that were fixed, which includes the new features can be found here.

Posted by Philipp Kewisch at 1:34 AM | Permalink | Comments (9)

Posted by Jan Bambach at 1:45 PM | Permalink

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.

Posted by Simon Paquet at 1:02 AM | Permalink | Comments (9)

But there were huge technical roadblocks in the way: could Mozmill automate the XBL-heavy calendar user interface? How reliable would any such automation be due to the way the views were drawn on the screen? How much time would it take someone to do it? None of us had the time or bandwidth to figure it out, so Philipp and I proposed it as a Google Summer of Code project and hoped that some brave soul would choose to volunteer for our project.

The brave soul that answered was Merike Sell, our Estonian localizer. She proved herself an incredibly skilled hacker, finding ways to make these tests work reliably on the Lightning UI across Windows, Linux, and Mac operating systems. She's even created a complete shared module of calendar utility functions to make it much easier for anyone to add new tests in the future.

To give you an idea of what types of automatic testing she completed, we have the following tests checked in to calendar/test/mozmill.

• Event Creation, Verification of Events in all Calendar Views
• Event Dialog Input Testing, including UTF-8 Input testing
• Task Dialog Input Testing
• Task Pane View testing
• Today Pane Testing
• Recurring event testing for Daily, Weekly, Monthly, and Yearly recurrences
• Recurring events are displayed properly in horizontal views
• Extremely detailed Timezone tests to check for the most common timezone bugs

Underlying these tests are a basic set of APIs in the shared module testCalendarUtils.js. These APIs can help you do everything from fill in an event dialog to verify that an event is in the correct location on the screen in each view. Merike has written some excellent documentation for the API as well.

We'd like to thank both Frank Hecker and the Mozilla Foundation as well as David Ascher and Mozilla Messaging for making this possible. And we'd like to thank and congratulate Merike on a job well done. She braved through completely uncharted waters, found a dozen Mozmill bugs and created the first complete set of calendar automated tests in the history of our project.

Thanks Merike!

Posted by Calendar QA Team at 3:54 PM | Permalink | Comments (1)

In February 2008 I wasn't even a user of Lightning yet as it becomes obvious from looking at my home calendar. Four months later I was researching how to translate it so I could have Thunderbird and Lightning in the same language because an Estonian localization didn't exist. A year later being familiar with the localization side of Mozilla and using Lightning regularly the option to write tests for calendar looked really appealing when I noticed it in the wiki. In April I found myself participating in the testday for Mozmill 1.1. (There's another one coming where you could participate by the way!)

Now that I've written smoketests for bug #500469 I find Mozmill relatively similar to Selenium as I expected. Both of these tools test user interface functionality and therefore the basic three types of steps are common to both:

• Locating elements to act on
• Specifying actions to be done
• Checking the results

Element location in a Mozilla application can be done either by using Mozmill's inspector which gives you a ready to use locator or with the help of DOM inspector if you need to access an element that is further down in the hierarchy of UI elements than what Mozmill's inspector gives you. Locators in Lightning are quite long but mostly relatively easily accessible. There are exceptions to this though: bug #505336 being an example of an element that is fighting against automation.

As UI responsiveness is always slower than script speed pauses between test actions are essential to let UI load properly. Failing to do that can result in an otherwise fine-looking test not working and once in a while I'm still able to forget that despite of knowing it. There are also some inconsistencies between platforms support of Mozmill which made it impossible to stick to the Linux environment I mostly use but it also gives both the Mozmill and Calendar development version stress on both platforms which can only make these more bulletproof.

Result checking is the most important part of functional tests even if running a test without any asserts can reveal some of the bugs too. This is also the part of Mozmill code that recently reminded me of just how quickly Mozmill is developed. I was looking for a way to assert that a certain element is not hidden and found a assertPropertyNotExist function by scrolling through the available methods on Google Code. This seemed like a good way to make sure that there's no hidden attribute attached to an element. To my surprise the first call to this method caused a failure which stated that there's no such function. It had been added only a couple of hours earlier and the version installed didn't have it yet!

Active development of Mozmill and fantastic people on both the #qa and #calendar IRC channels make the difference between a person merely checking things out and a new participant in the project. That's what it takes to get a new person to participate.

Posted by Simon Paquet at 12:40 PM | Permalink

Mozmill is a new UI automation tool for the Mozilla Platform. Mozmill can run either as an extension or as a command-line tool. So, once Merike finishes her tests, we will begin running these via command line, and having them automatically report their results either to the Calendar Tinderbox or some place else (It's up to the team).

The first step is to automate the basic smoke tests that we would normally run on a lightning build to be sure that everything is functioning properly. After that, she will move on to writing tests for more complicated scenarios such as recurring events, meeting appointments, and timezones so that we can be certain those critical areas are free from regressions.

We hope that Merike's valiant attempts to tame the uncharted jungle of calendar test automation will help others to follow in her path. Her tests are stellar examples of Mozmill tests, and they create a perfect starting point for anyone who would like to learn how to write these types of tests. We are looking forward to a great summer of automation.

Posted by Calendar QA Team at 1:15 PM | Permalink | Comments (4)

It's been three months since I last posted a donations update. And it's more than time to update our community on the current state of things, because two exciting things have happened or are about to happen.

1. Back in April we had accumulated roughly 1150$ of donations and we were heavily contemplating what to do with it. At the same time, a long-term localization contributor, Merike Sell, offered to create an automated testing framework for the calendar applications as part of Google's Summer of Code. Unfortunately the project was not accepted (only a few of the dozens of worthy projects were accepted by Google), but the offer was too good to let it slip.

   So we decided to use our money to fund Merike's project outside of Google's summer of code. Unfortunately our money was not enough to fund Merike for the three months period, but David Ascher (CEO of Mozilla Messaging) graciously agreed to cover the remaining 3350$.

   Merike is already hard at work. You can watch her progress in Bug 500469. Her mentor, Clint Talbert, will post an introductory posting explaining the overall goal of her project. And hopefully Merike will post here as well with a short introductory post and a status update once in a while.

2. The mozilla.org add-ons site has finally introduced the possibility to ask for donations (or contributions as they call them) directly on the add-on page of each participating add-on. The Calendar Project to participate in this program in the hope of increasing its donations through this avenue. Let me state clearly that these donations/contributions will be optional.

Let me close by aying "thank you" to everybody who has donated to the Calendar Project so far and to everyone who is planning on doing this in the future. As you can see, these donations can really do some good, so donate now!

Posted by Simon Paquet at 1:06 PM | Permalink | Comments (3)

Posted by Calendar QA Team at 12:00 PM | Permalink

Yesterday I finally managed something that I've been basically planning to do f or years: Fixing bug 456938.

As you can see from the updated holiday calendar page on our website, every holiday calendar is now annotated with its duration of validity. That will hopefully reduce the frustration that some of our users have felt, when they subscribed themselves to an outdated holiday calendar in the past. It will also make things much more easier for me to maintain the holiday calendar page in the future by enabling me to quickly determine whether a holiday calendar is still valid or not.

However the downside of this exercise has been that (as of the time of writing) I've identified 27 holiday calendars, which are outdated. I've removed those calendars from the holiday calendar page for now, but the old files are still in place so as to not deliberately break people, who have subscribed to them.

My plan right now is to delete the outdated files after a period of 2-3 months if no update materializes. It would be great if our community could step in here and provide updates for the remaining outdated holiday calendars.

It would also be great to get holiday calendars for those countries that aren't currently listed either on the holiday calendar page or the outdated holiday calendar buglist.

Posted by Simon Paquet at 5:07 AM | Permalink | Comments (1)

• Though we do not expect things to go wrong, we always strongly encourage you to back up your profile, and to do your testing on a "test" profile.
• Backing up a profile is easy:
1. Find your profile directory: Windows: %AppData%\Thunderbird, Linux: ~/.thunderbird, MacOSX: ~/Library/Thunderbird
2. Copy the root of it somewhere else, for example copy the Thunderbird directory and everything below it.
• Creating a testing profile is also easy:
1. Launch your application with a '-P' option from a terminal prompt.
2. Create a new profile by clicking the 'Create Profile' button.
3. Click 'Next', Give it a name like "Testing Profile", click 'Finish'.
4. Select the testing profile, and click the 'Start Shredder' button.
• Remember that you will have to start the application with the -P option during testing so you can pick your testing profile.
• Once you have finished testing, you can delete the extra profiles, and you will be back to normal. If something goes terribly wrong (although we do not expect it to), close the application, and just replace the profile with the backed up copy. That will reset the application to the way it was before you started testing.

Posted by Calendar QA Team at 9:21 AM | Permalink | Comments (6)

The next test day will be held on Thursday, November 13th. We want to put email-based scheduling (iTIP/iMIP support) to the acid test on our testday. Please keep in mind both are alpha versions! Therefore you should take following steps:

• Though we do not expect things to go wrong, we always strongly encourage you to back up your profile, and to do your testing on a "test" profile.
• Backing up a profile is easy:
  1. Find your profile directory:
     Windows: %AppData%\Thunderbird
     Linux: ~/.thunderbird
     MacOSX: ~/Library/Thunderbird
  2. Copy the root of it somewhere else, for example copy the Thunderbird directory and everything below it.
• Creating a testing profile is also easy:
  1. Launch your application with a '-P' option.
  2. Create a new profile by clicking the 'Create Profile' button.
  3. Click 'Next', Give it a name like "Testing Profile", click 'Finish'.
  4. Select the testing profile, and click the 'Start Shredder' button.
• Remember that you will have to start the application with the -P option during testing so you can pick your testing profile.
• Once you have finished testing, you can delete the extra profiles, and you will be back to normal. If something goes terribly wrong (although we do not expect it to), close the application, and just replace the profile with the backed up copy. That will reset the application to the way it was before you started testing.

There are also some fixed tb-integration bugs that need to be verified. You simply have to add a comment to the bug report stating what version and operating system you used while verifying the bug fixed.

The outcome of our last testday: 39 tests run and 11 marked 'failed'. Many thanks go to karora, whose comments in the failed test cases let us file two new bug reports.

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

Posted by Calendar QA Team at 4:55 AM | Permalink | Comments (7)

Two weeks have gone by and the Calendar developers are fixing bugs like crazy, as evidenced by the 44 bugs that we could fix in the last 14 days.

Because of the large amount of changes, we're asking everybody to go and download a nightly build and test it intensively and report all the bugs that you find in bugzilla.

As a reference, here's the list of the 44 bugs that were fixed within the last 14 days:

• Bug 281690: Days are shown two times in Minimonth (depending on timezone)
• Bug 303663: Should ICS calendar always bumps DTSTAMP on all events when writing?
• Bug 305432: Setting nativeTime sets timezone to UTC
• Bug 351880: Selecting repeating event in Unifinder does not select events in Main View
• Bug 358498: calAttendee::icalProperty bug with rsvp
• Bug 361634: imip-bar should consider local status of iTIP/iMIP invitations
• Bug 394902: Update libical
• Bug 401597: Provide Sunbird nightly updates via aus2-community.mozilla.org server
• Bug 412096: "New Event" button should have the same disabled state everywhere
• Bug 414949: Add AMO integration pane for Sunbird
• Bug 418345: Decide how to handle Generation property properly
• Bug 431127: Move email-specific itip processor code to the transport
• Bug 431383: Replace GIF with APNG throbber
• Bug 445769: iMIP bar isn't updated after declining an invitation
• Bug 446172: Add tentative invites to invites-counter
• Bug 450565: When accepting an invitation the 'Default alarm setting' is not considered
• Bug 452759: Tracking bug for 0.9 RC cleanup
• Bug 456354: Get rid of "Today" toolbarbutton
• Bug 456377: Integrate New Event, New Task into Write Button
• Bug 457024: Crash during shutdown
• Bug 457203: iTIP overhaul
• Bug 458190: Broken unit tests
• Bug 460263: Postflight on macosx fails when building thunderbird with lightning
• Bug 460408: Shutdown crash at nsXPConnect::GetRuntime()
• Bug 460649: Make use of new search textbox widget in unifinder
• Bug 461166: e4x parser borks on surrounding white spaces and certain response elements
• Bug 461328: Errors because chooseCalendarDialog.xul and calErrorPrompt.xul aren't packaged
• Bug 461337: Sunbird tinderboxen need more disk space to stay green
• Bug 461628: Failed to load jar:calendar.jar!/content/calendar/calendar-minimonth-busy.js
• Bug 461709: Remove ctrl-q for quit on Windows (like Thunderbird)
• Bug 461826: .ics attachments from Thunderbird/Lightning not compatible with iCal
• Bug 461941: [404] link to http://www.mozilla.org/projects/calendar/lightning/build.html
• Bug 461944: Selected event in unifinder is not highlighted in calendar view
• Bug 462026: 301 and 302 redirects not done properly with caldav provider
• Bug 462317: Crash [@strlen][@icalmemory_strdup] when closing a recursive event
• Bug 462393: Sunbird tinderboxen busted [Error: mozilla/dist/bin/js: Not a directory]
• Bug 462426: Throbber icon not visible in Customize Toolbar dialog
• Bug 462447: Remove CVS leftovers from new buildbot mozconfig files
• Bug 462490: Today pane -> 'new event' icon is defect
• Bug 462837: WARNING: Illegal character in window name prompt-occurrence-modification
• Bug 463060: Clean-up and move clipboard.js
• Bug 463067: Small icons for Cut/Copy/Paste toolbar buttons are truncated
• Bug 463079: Assertion failure, can't load any remote calendars
• Bug 463082: Update screenshot section to Sunbird 0.9 release

Many thanks go to all developers, contributors, localizers, testers, and supporters that make this possible.

Posted by Simon Paquet at 4:56 AM | Permalink | Comments (9)

The next test day will be held on Thursday, October 30th. This time we want to take a look at the Lightning trunk builds in Thunderbird 3.0b1pre again. Please keep in mind both are alpha versions! Therefore you should take following steps:

• Though we do not expect things to go wrong, we always strongly encourage you to back up your profile, and to do your testing on a "test" profile.
• Backing up a profile is easy:
  1. Find your profile directory:
     Windows: %AppData%\Thunderbird
     Linux: ~/.thunderbird
     MacOSX: ~/Library/Thunderbird
  2. Copy the root of it somewhere else, for example copy the Thunderbird directory and everything below it.
• Creating a testing profile is also easy:
  1. Launch your application with a '-P' option.
  2. Create a new profile by clicking the 'Create Profile' button.
  3. Click 'Next', Give it a name like "Testing Profile", click 'Finish'.
  4. Select the testing profile, and click the 'Start Shredder' button.
• Remember that you will have to start the application with the -P option during testing so you can pick your testing profile.
• Once you have finished testing, you can delete the extra profiles, and you will be back to normal. If something goes terribly wrong (although we do not expect it to), close the application, and just replace the profile with the backed up copy. That will reset the application to the way it was before you started testing.

The goal of our test day is to run as many Litmus test cases for Lightning as possible. If you find outdated or broken test cases, please leave a comment.

There are also some fixed tb-integration bugs that need to be verified. You simply have to add a comment to the bug report stating what 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

Posted by Calendar QA Team at 3:51 AM | Permalink | Comments (1)

• Participants: mschroeder, dbo, clarkbw, sipaq, fallen
• Simon (sipaq):
  • sent email to gozer about l10n builds for trunk: gozer mentioned pretty near to l10n builds for sunbird, lightning more complicated. Localizers keep on asking sipaq about localized builds
  • L10n work on Thunderbird, finding unused strings.
• Martin (mschroeder):
  • done some cleanup recently, removed gCalendarWindow
  • litmus test case cleanup with Andreas
• Daniel (dbo):
  • has been left sick most of the week, but started working again yesterday
  • more on iTIP overhaul
  • some investigations into recent tb/ltn crasher
  • thinks about a parentless occurrences solution
• Bryan (clarkbw):
  • Thunderbird:Activity_Manager (emre started to work on that)
  • search results (tab, exptoolbar)
  • POP3 disk usage options
• Philipp (fallen):
  • getting rid of the toolbar items, either just removing or replacing them
  • posted bugs about what needs to be discussed
  • everything P1 that's in work
  • probably after barcelona: unifinder tied to gloda/exptoolbar
• Simon reminds of blogging!
  • Daniel will try to write something up on the iTIP overhaul
  • Philipp will try to blog about the toolbar work or on integrating into gloda
  • Martin will come up with a topic by the weekend

Posted by Simon Paquet at 6:06 AM | Permalink

The next test day will be held on Thursday, October 16th. This time we want to take a look at the Lightning trunk builds in Thunderbird 3.0b1pre. Please keep in mind both are alpha versions! Therefore you should take following steps:

• Though we do not expect things to go wrong, we always strongly encourage you to back up your profile, and to do your testing on a "test" profile.
• Backing up a profile is easy:
  1. Find your profile directory:
     Windows: %AppData%\Thunderbird
     Linux: ~/.thunderbird
     MacOSX: ~/Library/Thunderbird
  2. Copy the root of it somewhere else, for example copy the Thunderbird directory and everything below it.
• Creating a testing profile is also easy:
  1. Launch your application with a '-P' option.
  2. Create a new profile by clicking the 'Create Profile' button.
  3. Click 'Next', Give it a name like "Testing Profile", click 'Finish'.
  4. Select the testing profile, and click the 'Start Shredder' button.
• Remember that you will have to start the application with the -P option during testing so you can pick your testing profile.
• Once you have finished testing, you can delete the extra profiles, and you will be back to normal. If something goes terribly wrong (although we do not expect it to), close the application, and just replace the profile with the backed up copy. That will reset the application to the way it was before you started testing.

The goal of our test day is to run as many Litmus test cases for Lightning as possible. If you find outdated or broken test cases, please leave a comment.

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

Posted by Calendar QA Team at 9:40 AM | Permalink

Our next testday will be on Monday, September 15th, and we will concentrate on the first release candidate of Lightning and Sunbird 0.9, which you can get here:

• Lightning 0.9 RC1:
  • Windows
  • Linux
  • Mac OS X
  • Solaris (Intel)
  • Solaris (SPARC)
• Sunbird 0.9 RC1:
  • Windows
  • Linux
  • Mac OS X
  • Solaris (Intel)
  • Solaris (SPARC)

We need your help to complete the remaining localization (L10N) checks, and the update testing, as you can see from the test plan.

The participation in the last Sunbird localization testday wasn't so good. Maybe it is helpful to clarify what L10N testing means. It is not really necessary to understand the tested language because the main focus of this testing is to find untranslated strings (still the English wording), garbled characters (language specific letters, e.g. 'ü' or 'ä'), and messages in the error console at startup (often caused by mistranslated timezone strings). Please, take a look at some of the bugs filed on the last testday, which are good samples: bug 449646 and bug 450618.

Localization testing in Sunbird is easy. After downloading and unzipping the translated Sunbird build start the application with a new profile, and you get the correct locale. In Lightning you should also use a new profile, but you have to start Thunderbird with the parameter '-UILocale', e.g. '-UILocale fr' or '-UILocale pt-BR'. So you get a French or Portuguese (Brazil) Lightning - independent from your Thunderbird locale. The RC1 build is multilingual and contains all shipped locales.

In earlier releases we found critical bugs in the update test scenario, and so this is the second major topic of the testday. Especially this time it is worth to check the timezone functionality after the update, because in 0.9 the timezone database is a separate add-on. You can also find a matrix with the update paths at our test plan. If you have anything to add, feel free to do so.

As usual there are also some fixed bugs that need to be verified. You simply add a comment to the bug report stating what product, version and operating system you used while verifying the bug fixed.

Join us in #calendar-qa on Monday. All the information on the test day is on our usual Test Day Wiki Page.

Hope to see you in #calendar-qa!

Andreas & Martin
Calendar QA Team

Posted by Calendar QA Team at 3:41 PM | Permalink | Comments (4)

Finally! The first release candidate (RC!) of our 0.9 release is available! I know you've been waiting a long time for it, so grab yourself a build. Here are the links:

• Lightning 0.9 RC1:
  • Windows
  • Linux
  • Mac OS X
  • Solaris (Intel)
  • Solaris (SPARC)
• Sunbird 0.9 RC1:
  • Windows
  • Linux
  • Mac OS X
  • Solaris (Intel)
  • Solaris (SPARC)

The Lightning builds contain all available locales (30). To download a localized Sunbird build, you'll need adjust the link and replace the "en-US" string with the locale code of your locale, e.g. "ko" for Korean.

We really need your help to complete the rest of the L10N Checks and the Update testing, as you can see from our Test Plan.

The Update Testing is of special concern to us, because historically this has always been where we have found critical issues in our release candidate builds. So, please take a look. Feel free to update the test plan wiki or leave a comment on this post with what you tested, so we can track what has been done versus what is still remaining to do.

If you have problems or questions, please drop by #calendar-qa on IRC.

Happy Testing!

Posted by Simon Paquet at 7:15 AM | Permalink | Comments (18)

The next test day will be held tomorrow, August 28th. In the light of Bruno's developer note, we decided that the main focus of this test day will be CalDAV. So, if you use a CalDAV calendar server, try with a recent nightly build of Sunbird or Lightning. But please backup your profile beforehand!

Please take a look at the CalDAV support matrix. This page overviews CalDAV servers supported by Sunbird and Lightning, and contains some additional information, e.g. where to download the server or how to configure a calendar client to exchange data with the server. If you have anything to add, feel free to do so.

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

Posted by Calendar QA Team at 8:00 AM | Permalink

One of the things we're excited about for the 0.9 release is the addition of CalDAV scheduling support. CalDAV scheduling is an emerging standard; the first widespread use of it was in Mac OS 10.5, where it allows iCal users not only to store their calendars on a shared server, but also check each other's free/busy schedules, send each other meeting invitations, respond to meeting invitations, and so forth.

With 0.9, people using Sunbird and Lightning will be able to do all these things, using not only Mac OS 10.5 servers but also a growing number of other CalDAV servers, both open-source and otherwise. And they'll be able to do so regardless of whether the other calendar users they are interacting with are using Sunbird, Lightning, iCal - or some other CalDAV client we haven't even heard of yet.

CalDAV scheduling support has just started to appear in nighlies over the last few days. It will be filled out further over the next few, but what it really needs most right now is TESTING! We're really hoping the community will give this new code a serious workout and help us find whatever bugs remain so that it will be rock-solid for the 0.9 release. As Daniel has noted, testing nightly builds can be dangerous to both your profile and your data - so be careful but please do bang at it and let us know what you find.

Posted by Simon Paquet at 4:20 AM | Permalink | Comments (3)

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...

Posted by Simon Paquet at 5:53 AM | Permalink | Comments (2)

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

Posted by Calendar QA Team at 2:35 PM | Permalink

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!

Posted by Simon Paquet at 2:06 PM | Permalink | Comments (2)

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

Posted by Calendar QA Team at 10:08 AM | Permalink | Comments (3)

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

Posted by Calendar QA Team at 10:05 AM | Permalink | Comments (7)

Our next test day will be held on Thursday, July 17th, and we need your help to find regressions and bugs!

I want to give you a short description how a test day proceeds:
We usually try a mix of Litmus and ad-hoc testing. Ad-hoc testing is testing where we attempt to use the product like a 'normal user' to find any issues that crop up along the way. We also try to make the application break by doing unexpected things - mixing up events, mails, tasks, calendar types etc. This is also called 'destructive testing'. After you have discovered a bug, you should take a look at the Error Console in the Tools menu before submitting a bug report, since it usually contains valuable information that points to the cause of the bug.
We also verify fixed bugs. In this case, we just add a comment to the bug report stating our used product, version and operating system.

Please, join us in #calendar-qa on Thursday. You can find all information on the test day on our Test Day wiki page.

Happy Testing!

Andreas
Calendar QA Team

Posted by Calendar QA Team at 2:22 PM | Permalink | Comments (6)

Yesterday we had a pretty interesting developer conference call, which was basically about the issue that only a very small team is currently developing on Lightning and Sunbird (basically just three people), that it is hard to reach community expectations with regards to bugfixes and feature work with so small a team and what would be necessary to attract more outside developers.

From my point of view one of our shortcomings in the past has been on the communication front. With that I don't mean the communication between different people on certain bug characteristics or code issues (that works great), but the communication between the calendar project and our community.

Currently our channels of communication are:

• This blog, which just gets a post every one to two weeks with a bug fix status update
• our developer and support newsgroups (mozilla.dev.apps.calendar and mozilla.support.calendar), which are not exactly buzzing with activity
• IRC, which not many people are watching

The result - at least as far as I see it - is that

• the core people from the project come across as a closed circle to which it is hard to get in to (the opposite is true)
• what's going on in the project is not exactly transparent. Instead I would call it opaque.

So what can we do to improve our situation, to make the project more transparent, to raise the interest in the project and by that to gain more outside contributors? A few things come to my mind:

• We need to talk more about what we are doing. Therefore every core contributor will try to commit himself to at least blog about various stuff at least once a week from now. These posts will probably range from developer-oriented topics (interesting or disgusting pieces of code, recent bugfixes, UI considerations, QA problems/successes/challenges) and project-related topics (PR issues, community relations, ...) to basically anything that the people find worthwhile to blog about.
  In my opinion a great example to follow here is the Firefox community. Where nearly everybody involved in the project (developers, build engineers, QA staff, PR and marketing people, management) tries to blog regularly about various Firefox stuff or other stuff that interests them. The outside image that this creates is the image of a beehive, where everybody is doing lots of stuff to improve Firefox and in my opinion stuff like this also attracts outside people, because everybody would like to contribute to a project that is alive and well instead of a project that is stalling or dead.
• We need to raise the awareness of the project in the outside world. I'll try to contact a few people to get some press contacts, in the hope to do some interviews with some people interested in open source. We hope that this will raise the awareness of Lightning and Sunbird and bring in outside contributors.

Posted by Simon Paquet at 3:48 AM | Permalink | Comments (27)

The test day held on Thursday, June 26th will be the first one in a series of test days and QA working sessions over the next weeks. This time, please help us to find the most hidden regressions. We suggest that you try Litmus and some ad-hoc testing to find regressions in any part of Sunbird or Lightning 0.9pre.

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 test day is on our usual Test Day wiki page. Happy Testing!

Hope to see you in #calendar-qa!

mschroeder
Calendar QA Team

Posted by Calendar QA Team at 11:55 AM | Permalink | Comments (1)

Our first test day after the release of Lightning and Sunbird 0.8 will be on Thursday, June 5th. Please help us find any new regressions and bugs. We identified some areas where we need your help testing:

• New dialog for modifying & deleting a repeating event
• 'Switch this calendar on' feature to disable a calendar completely
• iMIP/iTIP support (email based invitations)
• CalDAV calendar support

We suggest that you try a mix of Litmus and ad-hoc testing. Ad-hoc testing is testing where you attempt to use the product like a "normal user" to find any issues that crop up along the way. You also try to make the program break by doing unexpected things, just do anything you can imagine - mix up events, emails, tasks, calendar types etc. When you find something, take a look at the Error Console (especially before submitting a bug report), since there is usually very valuable information there that points to the cause of the bug.

There are also many fixed bugs that need to be verified. You simply 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 test day is on our usual test day wiki page.

Happy Testing!

Posted by Calendar QA Team at 2:36 PM | Permalink | Comments (10)

Our next test day will be on Thursday, March 20th. We will be testing nightly builds before creating a second release candidate for Lightning and Sunbird 0.8, there may even be a RC2 ready for the testday. Please help us find any stop-ship bugs that might still be hiding in both products. There is a ton of stuff to do:

You should have a look at our test plan for the release. If you are a localizer, try the recent builds and check your localized builds of Lightning and Sunbird. Your feedback by editing the table in our test plan is appreciated. We also need help to re-test localized builds with known (but now hopefully fixed) bugs.

We want to test migration from previous releases 0.3, 0.3.1/0.5 and 0.7 to 0.8. For these tests ask in #calendar-qa how to proceed. To ensure basic functionality for the release, general testing with Litmus and ad-hoc methods on all OS's must be performed.

As usual there are also some fixed bugs left that need to be verified. You simply add a comment to the bug report stating what product, version and operating system you used while verifying the bug was fixed.

Join us in the #calendar-qa IRC channel on Thursday. All the information on the test day is on our usual test day wiki page, and on the test plan.

Happy Testing!

Posted by Calendar QA Team at 3:39 PM | Permalink

The 0.8 RC1 is available! I know you've been waiting a long time for it, so grab your self a build. Here are the links:

• Lightning 0.8 RC1:
  • Windows
  • Linux
  • Mac OS X
  • Solaris (Intel)
• Sunbird 0.8 RC1:
  • Windows
  • Linux
  • Mac OS X
  • Solaris (Intel)

We really need your help to complete the rest of the L10N Checks and the Update testing, as you can see from our Test Plan.

The Update Testing is of special concern to us, because historically this has always been where we have found critical issues in our release candidate builds. So, please take a look. Feel free to update the test plan wiki or leave a comment on this post with what you tested, so we can track what has been done versus what is still remaining to do.

The test day today has been a great success, but we need to keep up the intensity and keep pounding on this build. It'd be great if we can make our next RC the final build, but we can only do that if we're sure we found all the issues with this RC.

If you have problems or questions, please drop by #calendar-qa on IRC.

Happy Testing!

Posted by Calendar QA Team at 4:35 PM | Permalink | Comments (38)

• Upgrade testing from previous releases (0.3.1, 0.5, 0.7) to 0.8
• Time zone support
• Task Mode Ad-Hoc testing
• Locale Testing (if we have localized builds available)
• General Testing with Litmus and Ad-Hoc methods

All the relevant information is up at the test day wiki page, and on the test plan. We hope to see you in the #calendar-qa IRC channel on Thursday March 6!

Onward to 0.8!

Posted by Calendar QA Team at 6:13 PM | Permalink

The handling of time zones in Sunbird and Lightning has greatly improved, and you should be able to import and subscribe to calendars created with other calendar applications without any problems. We also updated our internal time zones according to the recent official changes. You can test the functionality using calendars (also created with other software), and checking if the events and tasks are shown at the correct times in the calendar views and task list.

The new Task mode with its own toolbar in Lightning is one of the prominent features for the upcoming release. Please have a look at this feature, and try it out as extensively as possible.

When testing the experimental offline support and initial timezone guessing, please have a look at the Test Day Wiki Page for instructions. We are particularly interested in your experiences using the experimental offline support, whether positive or negative. Please add a comment to the end of the 'What specifically will we be testing?' section of the Test Day Wiki Page.

Our last test day has been a great success, especially the number of Litmus testcases run. Andreas Treumann used the feedback on unclear and broken testcases to improve those, and our testcases should be more up-to-date now.

We suggest that you try a mix of Litmus and ad-hoc testing. Ad-hoc testing is testing where you attempt to use the product like a "normal user" to find any issues that crop up along the way. You also try to make the program break by doing unexpected things, just do anything you can imagine - mix up events, emails, tasks, calendar types etc. When you find something, take a look at the Error Console (especially before submitting a bug report), since there is usually very valuable information there that points to the cause of the bug.

As usual there are also some fixed bugs that need to be verified. You simply add a comment to the bug report stating what product, version and operating system you used while verifying the bug fixed.

Join us in #calendar-qa on Thursday. All the information on the test day is on our usual Test Day Wiki Page.

Happy Testing!

Posted by Calendar QA Team at 6:49 PM | Permalink | Comments (5)

We are continuing to push on toward the 0.8 release candidate. In that vein, I'd like to make a special plea for testing. We are about to check in the code that will update the time zone database. Once that happens, we need you to do two things:

• TEST: We could really use your help in testing this. You know your own time zone far better than we do, so make sure your calendar switches into and out of summer time (or doesn't switch at all) at the appropriate dates for this year.
• BACKUP:If you have been running the 0.8 nightly builds, then you MUST backup your local (non-network) calendars (export them to ICS) BEFORE upgrading to a build with this change in it. The details are in bugzilla, but if you are running some of the 0.8pre builds, then this change might break your calendar when you update to the latest nightly.

What if I am running 0.7 (or earlier)? In that case, you are fine. You should be able to upgrade to 0.8 with no problems. Of course, it is always a good idea to periodically backup your calendars anyway. This issue occurs because we don't support upgrades between nightly versions, only between released versions of the software.

That said, we know a number of early adopters have already made the switch to 0.8pre builds and we want them to be aware of this potential issue.

Posted by Calendar QA Team at 11:18 PM | Permalink | Comments (1)

We identified some areas where we need your help testing both products:

• The unifinder (aka event list) has been partly rewritten, and we have already found (and fixed) some regressions.
• The handling of non-native timezones in Sunbird and Lightning has greatly improved, and you should be able to import and subscribe to calendars created with other calendar applications without any of the prominent problems, like shifting start and end times in the event dialog and calendar views. We will provide one or more calendar files with non-native timezones for testing on our Test Day Wiki Page.
• Every aspect of task related functionality in Lightning, especially the Task mode.

For testing our new features, the experimental offline cache and initial timezone guessing, please have a look at the Test Day Wiki Page for instructions.

We suggest that you try a mix of Litmus and ad-hoc testing. Ad-hoc testing is testing where you attempt to use the product like a "normal user" to find any issues that crop up along the way. You also try to make the program break by doing unexpected things, just do anything you can imagine - mix up events, emails, tasks, calendar types etc. When you find something, take a look at the Error Console (especially before submitting a bug report), since there is usually very valuable information there that points to the cause of the bug.

As usual there are also some fixed bugs that need to be verified. You simply add a comment to the bug report stating what product, version and operating system you used while verifying the bug fixed.

Join us in #calendar-qa on Thursday. All the information on the test day is on our usual Test Day Wiki Page.

Happy Testing!

Posted by Calendar QA Team at 11:14 AM | Permalink | Comments (9)

Posted by Simon Paquet at 12:02 PM | Permalink | Comments (2)

Lightning users should pay attention to the new drag&drop-conversion feature, i.e. you can transition items between tasks, events, and emails from one to the other by dragging & dropping them to the matching mode toolbar button. Andreas Treumann created a brand-new set of Litmus testcases for this feature (Lightning FFTs, Subgroup 'Drag and Drop' in Litmus).

We suggest that you try a mix of Litmus and ad-hoc testing this time. Ad-hoc testing is testing where you attempt to use the product like a "normal user" to find any issues that crop up along the way. You also try to make the program break by doing unexpected things, just do anything you can imagine - mix up events, emails, tasks, calendar types etc. When you find something, take a look at the Error Console (especially before submitting a bug report), since there is usually very valuable information there that points to the cause of the bug.

As usual there are also some fixed bugs that need to be verified.

Join us in #calendar-qa on Thursday. All the information on the test day is in our usual Test Day Wiki Page.

Happy Testing!

Posted by Calendar QA Team at 11:09 AM | Permalink | Comments (5)

• Task mode (Lightning only)
• Event list aka unifinder for Lightning
• Seperate Calendar mode menu (Lightning only)
• New alarm dialog
• Alarm indicator icons in the Calendar views
• Backend fixes to improve e.g. timezone handling and tasks

We suggest not to use the rather out-of-date Calendar testcases on Litmus but ad hoc testing. Some of you might ask, how this should work. Ad hoc testing is part of exploratory testing and less formal than you are used to with Litmus. You try to find bugs with any means that seem appropriate, and simply check out the different features. Important things, i.e. bugs, can be found quickly, because it is performed with improvisation. Always have a look at the Error Console (especially before submitting a bug report), there could always be valuable information for our developers.

As usual there are also some fixed bugs that need to be verified.

So, join us in #calendar-qa on Thursday. All the information on the test day is in our usual Test Day Wiki Page.

Happy Testing!

Posted by Calendar QA Team at 3:00 PM | Permalink | Comments (7)

In order to review the plans and to parcel out the work, we're going to discuss this at the next two QA Chat IRC meetings. These meetings occur at 17:30 UTC (click to find the time in your zone). The next one will be tomorrow, November 15. And the following one will be November 22.

Several great folks have stepped forward to help out, and we're looking forward to making this a success. If you are waiting for to get involved, then wait no longer! We will have lots of tasks from writing code samples, to writing documentation, to doing publicity.

I imagine that for most people out there, talking and learning about test automation doesn't sound like much fun. We're going to talk more about this when we start doing the big publicity for this event, but I'll let you in on a secret. We're going to be working on XPCShell tests, which are written in JavaScript. We're going to be teaching you what you need to know about JavaScript to be effective.

JavaScript is the heart of anything built on the Mozilla platform. That means that if you've always wanted to learn how to write a patch or an extension for Firefox, Thunderbird, Sunbird, Songbird, Seamonkey etc, then you will need to know JavaScript. This event (and learning by helping us prepare for the event) will help you get some hands on practice with the basics of JavaScript and start you on your way.

So, keep that in mind, we'll be talking about it more in the coming weeks. I hope to see you at the QA Chat in #calendar-qa.

Happy Testing!

Posted by Calendar QA Team at 8:17 PM | Permalink | Comments (2)

While reading LpSolit's article about the number of people fixing bugs on Bugzilla I thought that I should try to do the same for Calendar. Unfortunately this didn't really work as a lot of our fixed bugs were never assigned to the person who developed the fix and that completely screws our numbers.

So I thought of a second-best option: The overall number of bugs fixed per quarter for the last five years (click to enlarge):

What the numbers (and especially the moving average) clearly show is that we've been picking up some serious steam and are more active than ever.

Posted by Simon Paquet at 8:02 AM | Permalink | Comments (8)

We already found three show-stopper bugs, and that's why we had to reschedule the test day from Tuesday to Thursday. The new build is being crafted, and will be ready for us on Thursday. There are three things that must be tested:

• We must spot-check each locale to verify that they display properly (you can do this even if you can't read that language).
• We must make certain the bugs we found (399433, 399616, and 399780) were fixed properly. Note that these were all found by people just like you: you can make a difference!
• We must make certain no new bugs were introduced when those were fixed

We hope to see you on Thursday the 18th in #calendar and #calendar-qa. Come join the excitement and be a part of the 0.7 release.

See you Thursday!

Posted by Calendar QA Team at 10:09 PM | Permalink | Comments (5)

We need your help to deliver a good quality release.

So, join us in #calendar-qa on Tuesday. All the information on the test day is in our usual Test Day Wiki Page.

Happy Testing!

Posted by Calendar QA Team at 5:18 PM | Permalink | Comments (5)

In today's nightly build for Sunbird and Lightning, the fix for the "Publishing Events Bug" has landed. This bug has plagued people in 0.5, and we wanted to address it in 0.7. However, fixing it was complicated by how many different ways the bug can manifest itself.

We'd like to ask everyone that's seen this issue to retest their configurations with the latest nightly. This way we can determine if the patch fixed all the issues.

Technical Details

• Bug 387559: Main Tracking bug, event creation fails if server requires authentication for PUT but not GET
• Bug 391383: HTTP authentication doesn't work for world-readable, write-restricted ICS shares
• Bug 380291: Event movement failure on local or remote events
• Bug 390084: ssl problem: checking task on remote calendar return fatal error 0x80040111
• Bug 379498: WebDAV publish not publishing every time.
• Bug 380746: webdav write failure if HTTP AUTH needed for PUT but not GET

Thanks for your help in checking out this issue. If you find a problem, please add a comment to bug 387559. If you find other crazy behavior, please file a new bug. If you have any questions please ask them in #calendar or #calendar-qa on IRC and we'll try to help.

Thanks again for your help and happy Testing!

Posted by Calendar QA Team at 11:21 AM | Permalink | Comments (4)

They agreed to check in next week and make a decision, and the following wager was made.

• If Simon is right, Daniel must buy him a bottle of Single Malt Scotch
• If Daniel is right, Simon must buy him a case of his favorite German beer

The QA team has been watching the state of the project closely, keeping track of blockers and proposed blocking bugs as they are filed. This Tuesday, the QA team is doing intensive testing to gather data on the quality of Lightning and Sunbird. This information will enable the calendar team to make the crucial decision on Wednesday about the 0.7 release.

No one wants to slip the date. That said, we also want to release the highest quality product we can for 0.7, so if we have to take a week or two to ensure that, we will. We need your eyes to help us scrutinize Lightning and Sunbird on Tuesday, September 11. We need your help to ascertain the quality level of both products.

We'll take all the data we generate -- bugs, feelings, observations, etc -- and post them here in a Test Day Findings post. That information will be used in the Wednesday Status call to figure out whether Simon will be drinking Scotch, or Daniel will be drinking beer.

So, join us in #calendar-qa on Tuesday. All the information on the test day is in our usual Test Day Wiki Page. Let's figure out where we're at, and when we're going to release 0.7.

Happy Testing!

Posted by Calendar QA Team at 10:23 AM | Permalink | Comments (13)

One of the most exciting features to land in time for this test day is the resolution to the War On Boxes bug. This means that your events will now take up the entire width of the week and day view area until they collide with another event at the same time. This graphic shows it decently well. For a better view, install the nightly build and come to the test day!

Come out to the test day and celebrate with us as we take the new and improved day and week views through regression testing and bug verification. We hope to see you in #calendar-qa on Tuesday, August 28th. For all the details, please see our Test Day Wiki Page.

Happy Testing!

Posted by Calendar QA Team at 5:11 PM | Permalink | Comments (3)

Number One: There will be a QA working session on Monday, August 13th at 13:30 UTC. We'll go through the list of unconfirmed enhancement bugs and discuss them to see what's suitable for the 1.0 release.

Number Two: Our last test day was a success, and we had some first time testers in #calendar-qa. Thank you for contributing to our QA effort. Without you it wouldn't be possible. So, we're holding our next test day on Tuesday, August 14th and hope to see you again. This time we'll try to confirm bugs on our unconfirmed list. It includes checking what other users have reported and possibly creating simpler steps to reproduce the bug. You can find all the information on our Test Day wiki page.

We look forward to seeing you in #calendar-qa on Monday, August 13th and Tuesday, August 14th.

Happy Testing!

Posted by Calendar QA Team at 4:21 PM | Permalink | Comments (2)

Posted by Calendar QA Team at 4:34 PM | Permalink | Comments (3)

The former prototype event dialog has been promoted to be the new standard event and task dialog for Lightning and Sunbird. The developers are interested in feedback and bug reports of the test community to improve the new dialog. Also, the new Lighting "today pane" has landed, and we need your help testing it and the mail/calendar switch.

You can find all the information on our Test Day wiki page. We look forward to seeing you in #calendar-qa and Litmus on Tuesday, July 31st.

Happy Testing!

Posted by Calendar QA Team at 4:09 PM | Permalink | Comments (9)

Also, several user interface improvements have landed in Lightning, including the new mail/calendar switch and the "today pane". Join us to check out the new features and find any regressions these massive landings have caused.

As usual you can find all the information on our Test Day wiki page. We look forward to seeing you in #calendar-qa and/or Litmus on Tuesday.

Happy Testing!

Posted by Calendar QA Team at 10:56 AM | Permalink | Comments (2)

• ICS/WebDav: It seems that most of these problems stemmed from incompatible Limit/LimitExcept statements and a change to our code base that causes writes to fail if authentication is required for PUTs but not GETs. This is best summed up in bug 387559
• ICS/WebDav and CalDav: There are also proxy issues affecting both clients for these server types. The proxy configuration seems to have been recently broken, with various reports stating that it worked in 0.3.1 and that it did not work in 0.3.1. We need further clarification on this issue. This issue is summed up in bug 373439

We were able to track down the first issue to a specific check-in, and that is now being investigated. However, we need to do the same with the proxy issue. If you have a proxy configuration please try out various Lightning nightly builds and see if you can determine the build where the proxy configuration stopped working.

Things We Could Use Help With

• Determine the date the proxy configuration stopped working as mentioned above.
• Look at the list of these new remote calendar bugs, and see if we can duplicate some against others (leave us comments in the bug about your ideas).
• Give us suggestions on how we can improve calendar QA

Thanks very much to everyone that turned out for the test day. And congratulations to Alan Schwartz who won the prize for most creative test.

Happy Testing!!

Posted by Calendar QA Team at 5:22 AM | Permalink | Comments (7)

This test day is going to be different because we're encouraging everyone to get creative with their testing. See if you can help us find out why these events are disappearing. Take a look at Litmus, and see what we tested there, then think about ways to go beyond that. On Tuesday, we'll be giving an award for the most creative and effective test, so be sure to add your test to the Test Day Wiki page.

We've been doing a great job as a QA team, but I think this issue gives us an opportunity to think about how we can improve the quality of Lightning and Sunbird. I don't believe that the only solution is to quit our day jobs and work on this around the clock (although that might work).

I think we can find ways to work smarter, to do more with the time and the people we have. Maybe we should look into automating some of the testing. Maybe we should look at the weak parts of our Litmus test suite and fix those areas. Maybe we need to delve deeper into performance and memory leak profiling.

We have started this wiki page for brainstorming ways to improve every aspect of calendar QA. We're going to take your ideas, prioritize them based on what we need the most before 0.7 and put them onto our revised Calendar QA ToDo list.

We will see you on Tuesday. Get creative, bring us your best tests, and prepare to discover where all those events have gone.

Posted by Calendar QA Team at 7:04 PM | Permalink | Comments (8)

At long last, the 0.5 RC's are ready! We have the Sunbird RC's for all our supported locales as well as the Lightning RC's for all our supported locales AND a Lightning Universal Mac build.

We are truly happy to have this finally done. But, now is where we need your help. We've been in total lockdown for some time on this release, so we think the actual code bits are OK. But, this is the first time that the localizers (and anyone) has seen the localized Lightning builds.

We need your help to verify the localizations

We are holding a Localization test day on Friday, June 1 from 1200 UTC to 0100 UTC. Please drop into the #calendar-qa channel to help us test the localized builds and ensure that we can quickly ship the 0.5 that we have all been waiting for.

Here's where to get your hands on the RC:

• Lightning 0.5 RC 1
• Sunbird 0.5 RC 1

Thanks to everyone who has helped with this release. And, an even bigger thank you to everyone who has waited for us to release it. Thanks!

Happy 0.5!

Posted by Calendar QA Team at 11:03 PM | Permalink | Comments (23)

• 30 people took part
332 tests were run
• 90% coverage in litmus on all tier 1 platforms (Windows, Linux, Mac Intel, Mac PPC)
• 9 non-duplicate bugs found.

First place and the prize of the test day went to ssitter with over a hundred tests run in addition to serving as a moderator on the channel. Ray swept in with a close second at 59 tests and several good bugs. Andreas was on his heels with 54 tests. While these guys may have been in the lead, everyone's contribution helped us achieve 90% test coverage, and that's what I'm so excited about.

Several good bugs were found, but none of them were serious enough to block the release. We are still testing, of course, but so far everything looks good. The team is currently in the process of cutting the release builds which will include a localized Lightning and a universal Mac build of Lightning. No code changes are going in, so once we have the release build built, we will do a localization and functional test day. If we don't find any blockers, we'll release that as 0.5.

We are getting down to the wire, so keep an eye on this blog, the newsgroup, and Mozilla Zine for the announcement about the next test day. I'm going to try to have it on Tuesday, but it entirely depends on when the release is built.

I'm not sure what a virtual round of applause sounds like, but we should give ourselves a hand. This was a magnificent feat! Thanks to everyone that joined the test day effort and helped out. Thanks also to our moderators who in put in long hours to stay awake and available through the day. We couldn't do it without you!

Happy Testing!

Posted by Calendar QA Team at 8:22 PM | Permalink | Comments (12)

All questions about my sanity aside, we need a test day. The last of the 0.5 blocking bugs was fixed by Mr. Goold (thanks very much!). We are going to try to spin up a real release (including locales and everything) for both Lightning and Sunbird. But, even if that doesn't happen by tomorrow, we still need to test the code since these current branch nightlies are going to be the RC.

There will be rewards for this test day! I will announce the winner in this forum after they are announced at the Thursday Calendar QA Chat on May 17.

I know the project has been slipping a bit due to the hectic schedules of the core team, but we are trying very hard to keep it moving forward. The best way for you to help us is to participate in the test days. The regression testing is the last thing we need to do before we release 0.5, so the sooner it's finished the sooner we release. And that's exactly why we need your help tomorrow.

Thanks very much. Happy Testing and Good Luck!

Posted by Calendar QA Team at 10:12 AM | Permalink | Comments (13)

The QA Work Session will take place at 14:00 UTC time in the #calendar-qa IRC channel. The Test Day tomorrow will start at the usual 13:00 UTC, you can always find more information on the test day at our Test Day Wiki.

Every test we run and every bug we verify brings us that much closer to our 0.5 release. Thank you very much for your help. We look forward to seeing you tomorrow in #calendar-qa.

Happy Testing.

Posted by Calendar QA Team at 11:45 AM | Permalink | Comments (6)

Drop by #Calendar-QA and join the bug hunt tomorrow. If you can't make it tomorrow, we hope to see you at some point before the end of the week (Drop in for our QA Chat).

For tomorrow's test day we are going to drive it based on the testing recommendations at our Calendar Todo List. I will put together the standard test day wiki page later today. Thanks for your help.

Happy Testing!

Posted by Calendar QA Team at 7:51 AM | Permalink | Comments (7)

We've had two test days since my last post: one on March 20 and the other back on March 6. Both of these were great days. We had hundreds of Litmus Cases run, found several new bugs. Skuribay won the test day on March 6 and Thorn won the test day on March 20. Congratulations to you both!

Function Testing Begins!

As you can see on our new project calendar, Functional Testing for the 0.5 release will begin on Monday, March 26. We need folks to start running through the FFT (Full Functional Tests) in Litmus for both Sunbird and Lightning builds. Please help us cover as many OS's (windows XP, windows Vista, Mac OS X, Linux flavors etc) as we can on these tests. It is important for us to find as many bugs as we can before the string freeze as possible, so that the localizers have solid builds to work with.

We will be also holding a "Hard Core QA Session". This will be from noon UTC to 16:00 UTC on Wednesday March 28. We'll be working on QA Wanted and QA Discussion Needed bugs, to clear those out. Should we finish that, we'll work on functional testing of some of the newer components and features that have landed.

This is a great chance for folks to drop by and help with some of the core issues of bug triage and deep testing. We'll be holding several sessions like this in the coming days. Working with the QA Wanted and difficult defects will give you insight into how best to track and find issues, which will help you win test days and make the calendar code more robust.

It is time to ensure that we release the best possible product we can for 0.5, and that begins right now. We need to amplify the QA on Calendar. So, turn up your favorite music, download a nightly, and see how badly you can break it. If you find an unreported issue, drop us a bug.

I'll see you in #calendar-qa. Happy Testing.

Posted by Calendar QA Team at 3:25 PM | Permalink

Posted by Simon Paquet at 1:36 PM | Permalink

This is going to be a fast release, and the date that we release 0.5 will depend on how fast Calendar-QA can churn through our testing. To keep us organized with the upcoming test days and the release schedule, we have created the first project calendar for Sunbird/Lightning..

The March 6 Test Day marks the beginning of an exciting drive to release. Even more cool features will be landing in the next few days. We will need everyone's help to ensure that these features land intact, and that they work the way we all want them to. If you've got a day or an hour free, stop by the test day, stop by #calendar-qa. Come help us make the most exciting release for Sunbird and Lightning into something truly spectacular. We'll see you on Tuesday, March 6 at the Test Day.

Happy Testing!

Posted by Calendar QA Team at 6:38 PM | Permalink | Comments (13)

Now, those bugs are fixed, and we have spun the release candidate 2 (RC2) build. This will be the 0.3.1 release build if it passes our final round of testing. So, one more time, we need your help to run through the localization matrix, timezone tests, and the regression testing on the 0.3.1 RC2 build. You can see what needs to be tested on our 0.3.1 RC2 test tracking wiki page. As you run tests, please feel free to update that page with your findings.

Thank you very much. Let's get 0.3.1 out the door!

Posted by Calendar QA Team at 1:41 PM | Permalink | Comments (4)

As a result, we are extending the test day through the weekend. If you have a chance, please take a build and run it through our small suite of Localization tests in Litmus.

I have summarized all the information about where we stand on the test day wiki Using that table, you can determine which builds need to be verified and which have already been done. Localizers, you can use that same table to see if you have any issues you need to fix before we spin release candidate 2. We filed bugs for all the issues we found, and those bugs are listed there.

I am extremely encouraged and excited about your response. Today the #calendar-qa channel broke its own record of 30 people involved during a test day! Please keep it going--we need to get all these localizations tested before we push to the final release.

Thank you very much for your time and energy.

Happy Testing!

Posted by Calendar QA Team at 8:22 PM | Permalink | Comments (7)

We are very close to release of 0.3.1. Please join us for this final push. You can find all the information about the test day here: http://wiki.mozilla.org/Calendar:Current_QA_TestDay

Thanks for your help.

Posted by Calendar QA Team at 8:48 AM | Permalink | Comments (5)

• 2 Test days
• 29 People Involved
• 13 Bugs --> 4 stop ship on 0.3.1
• 341 Tests run! (315 Passed, 22 Failed, 4 Unclear)

This is a massive accomplishment. We also attempted to do some public announcements about the test day, and we owe xFallenAngel and Archaeopteryx thanks for their stellar efforts putting that together. We can thank Damian for the fact that there were only 4 unclear tests on these two test days. Thanks go out to eor who organized the second test day. Thanks to lilmatt and dmose who worked around the clock fixing bugs as fast as we found them. And a huge thank you to all the testers and moderators: andrewaclt, bbbrowning, jminta, beb, maarten, mschroeder, nightrat, skuribay, ssitter, ulf, paulivanov, excessory, matthaeus123, elichak, vanessa, zero_, tiago, frac, tomcat, asztal, mvillalo.

The winner of our test day is pretty new to the calendar-qa project. In addition to some great testing, he has worked to help broaden and build the calendar-qa community. Thank you and congratulations to Archaeopteryx.

As a direct result of all our good work, the February 2nd (tomorrow) build will likely be the 0.3.1 release candidate. So, we are not out of the woods yet. I will be holding a QA Work Session in #calendar-qa on this Sunday and Monday at noon UTC onboth days. Those sessions will go for two or three hours and we will concentrate testing on 0.3.1. Please join me if you have the time. On Monday (Feb.5), we will decide whether or not to hold another Test Day before 0.3.1 is officially released.

Thank you very much for your time and your help. I am happy to see the 0.3.1 release moving as quickly and as smoothly as it has. It couldn't have happened without your support.

Happy Testing

Posted by Calendar QA Team at 3:18 PM | Permalink | Comments (10)

And that is why we need you. We have to do testing on Sunbird and Lightning 0.3.1, and we have to continue our testing on Sunbird and Lightning 0.5 as well. So, we are having two test days next week. Our primary test day will be on January 30th, and a secondary test day will be held on February 1st. Click here for more information on those dates.

To underscore the importance of the January 30th test day, I'm happy to announce that we WILL have a reward for the hard working winner of the test day. It will be a Mozilla Store gift certificate. We will announce the winner of the test day at our QA Chat on February 1st.

If you've been wanting to try out a Mozilla test day, if you've been waiting to get involved, this is the perfect time to jump in. We will need all hands on deck as we release 0.3.1 and move quickly toward 0.5.

Thank you very much for your help. We hope to see you either on January 30th or February 1st, or both!

Posted by Calendar QA Team at 12:51 PM | Permalink | Comments (2)

RESULTS:

• 18 new bugs logged!
• 208 Litmus cases passed
• 19 failed
• 30 marked unclear
• Reported your UI feedback to the Calendar Status meeting.

Join us on #calendar-qa as we announce the winner of the test day at tomorrow's Calendar QA Chat.

Thanks for the help yesterday. Let's keep this momentum as we get closer to the 0.5 release. Mark your calendars for the next test day: January 30. We hope to see you there.

Posted by Calendar QA Team at 9:29 AM | Permalink | Comments (3)

The Test Day will be twelve full hours of Views testing and UI feedback bliss, starting at 13:00UTC on January 16 to 01:00UTC on January 17. You can find more information at http://wiki.mozilla.org/Calendar:QA_TestDay:2007-01-16

We are proud to announce that we will offer rewards again as we get closer to releasing 0.5. We will start with fun rewards first and progress to serious ones as the release nears.

So, whether you log in to give feedback on something or you run a test, we hope to see you in #calendar-qa on January 16.

Posted by Calendar QA Team at 1:10 PM | Permalink | Comments (3)

• 5 new people!
• 6 new bugs!
• 31 Remote calendar Litmus tests ran (2 failed, 1 unclear)

Congratulations to our top two testers: Jallison and Archaeopteryx! This was their first calendar test day and they did an excellent job! We had a lively test day with lots of contributors. Thanks to everyone involved: jayelix, ulf, ssitter, mschroeder, maarten, xFallenAngel, dror, bbbrowning, jminta, lilmatt, archaeopteryx, jallison, sipaq, mvl, setr, fopper, mechtilde, and damian. Come join us for our next test day on January 16.

Posted by Calendar QA Team at 12:00 PM | Permalink | Comments (8)

We wish you a happy new year, and we can't think of a better way to kick off 2007 than spending a few hours working with your favorite calendar project. We hope to see you on January 2nd.

For dates, times, details, and all of that, please turn to our ever faithful wiki page: http://wiki.mozilla.org/Calendar:Current_QA_TestDay

-- Calendar QA Team

Posted by Calendar QA Team at 1:10 PM | Permalink | Comments (10)

• 35 Litmus Test Cases Run
• 3 New Bugs Found

Due to the lack of advance notice, we had a very light test day. However, the folks who attended did very good work. We will have another "Remote Calendar Test Day" because remote calendars still need quite a bit more testing. Thanks to everyone that participated: Ulf, Andreas, Ssitter, xFallenAngel, Omar_public, Jminta, Lilmatt, UnLoGiC, Mechtilde, Ghoulio, Ogirtd, TFDuesing, Maarten, and Dmose.

Our next test day will be January 2nd. My new year's resolution will be to make our test days more interactive and more fun. I'm currently brainstorming ways to do that, and I welcome any ideas you may have. If you've got an idea, please post it in a comment to this thread. I will post my ideas once I organize them, so you can see them and send me suggestions.

I look forward to seeing you in the new year as we drive toward our next release of Sunbird and Lightning in early 2007. Please have a happy holiday and a wonderful new year's. I'll see you on January 2nd.

Posted by Calendar QA Team at 8:54 AM | Permalink

Please see http://wiki.mozilla.org/Calendar:Current_QA_TestDay for more information.

Thanks,

Calendar QA Team

Posted by Calendar QA Team at 3:32 PM | Permalink | Comments (2)

We ran a complete regression on both Sunbird and Lightning, ensuring that the recent database patch did not have any unintended side effects. We were also able to focus testing energy on the new prototype dialogs that the Sun team has been implementing. I'd like to thank everyone who was involved for their continued (and new) contributions: xFallenAngel, Sebo, Ulf, Andreas, Nightrat, Ssitter, Koenh, Matthaeus123, Fopper, Nor123, Soupes, Mechtilde, Mschroeder, Celina63, Dmose, Jminta, Lilmatt, Sandos.

We also held a mini-test day on December 1st with 22 students from Seneca College in Toronto. In a whirl-wind effort, they confirmed 16 unconfirmed bugs and filed 6 defects in 45 minutes! We are looking forward to working with the Seneca students again next semester.

Our next test day will be December 19. We will dedicate this day to testing the various types of remote calendars that Sunbird and Lightning can use: FTP, CalDav, WebDav, WCAP. As a holiday gift to the entire community, a new remote calendar provider might be available for testing on the 19th. You can either stay tuned for more information on that, or you can get a sneak peak by volunteering to aid with the preliminary smoke-testing of the new provider (assuming it lands). To volunteer, just drop by the #calendar-qa channel.

Thank you very much for the excellent test day on the 5th. We could not do it without you.

See you on the 19th.

-- Calendar QA Team

Posted by Calendar QA Team at 2:44 PM | Permalink | Comments (4)

The Test Day wiki page will be landing today in its normal location.

Remember you can always find ways to help out by checking out our Calendar QA ToDo List

We look forward to seeing you on December 5th.

-- Calendar QA Team

Posted by Calendar QA Team at 8:26 AM | Permalink | Comments (2)

Thanks very much to everyone that helped out, especially Matthaeus123 who ran 173 of those Litmus testcases! Thanks also to everyone that wrestled with the migration wizard code: Sebo, Ssitter, Koen, Unlogic, Nor123, Celina63, Jminta, Lilmatt, Mc, Mat75, and Matthaeus123. Thanks also to xFallenAngel for his calbot bot.

We found several issues in the migration wizard code, and even rebuilt the patch to fix dead-broke issues halfway through the test day. Next time we have a test day focused on brand new functionality, we will ensure the functionality is smoke-tested prior to the test day. We are also going to change the times for the test day so that the day better corresponds to when the nightly builds run. This should help clear some confusion surrounding "which build do I test with". Thanks again to everyone that participated. We're going to take a week off from test days, so we can make these changes. Our next test day will be December 5th. We'll see you on the 5th!

Happy Testing.

Posted by Calendar QA Team at 8:40 AM | Permalink | Comments (5)

The Calendar-QA team plans to celebrate these new features with an entire test day focused specifically on the new functionality, and we'd love for you to join us. The test day will be on November 14, from 01:00 (UTC) to November 15, 00:00 (UTC), that's 23 full hours of testing. For this test day, we will be returning to our Litmus Testing System, so it will be very easy for everyone to contribute. Please refer to the test day wiki for more information.

Additionally, the Calendar-QA team has already begun planning for our next test day. If you'd like to help out with that effort, please drop by the #calendar-qa (irc://irc.mozilla.org#calendar-qa) channel this week and let us know.

We hope to see you in #calendar-qa on November 14th.

Posted by Calendar QA Team at 9:41 AM | Permalink | Comments (2)

The Calendar QA Team had a successful test day on Tuesday.

• 57 total bugs addressed
• 3 new bugs found

We were able to confirm about 20 bugs, and we addressed (asked for more information, reassigned components, works for me, verified fixes etc) over 30 bugs. In the course of the day, we found 3 new bugs.

Thanks to everyone that helped out. The list of helpers has gotten so long, I'm sure I'll miss someone, and I apologize. But, thanks to: jminta, lilmatt, ssitter, celina63, sebo, nightrat, xfallenangel for moderating and helping set up the test day. Thanks also to all the folks that participated: lambert, mad-max, worzel, mc, mschroeder, unlogic, koen, damian, mattheus123.

Congratulations to our Winners!

Once again, our friends at Linpro AS have agreed to sponsor the prizes for the test day. This was a close race and we nearly had a tie, but the winners are:

• mschroeder
• damian

Thanks to everyone that helped out, and I look forward to seeing you at our next test day on November 14th.

Posted by Joey Minta at 6:48 AM | Permalink | Comments (10)

Posted by Calendar QA Team at 10:24 AM | Permalink | Comments (12)

• Apple iCAL
• Evolution
• KOrganizer
• Google Calendar
• Trumba
• The new Google Calendar Provider by our own xFallenAngel (not technically a third party product)
• Novell Groupwise 7
• Microsoft Outlook 2003

Posted by Calendar QA Team at 7:21 AM | Permalink | Comments (13)

In light of the recent 0.3 release, we've seen quite a few bugs coming through as people try to load data into Lightning and Sunbird from their favorite clients. We're going to have an entire test day focused on interoperability testing on Tuesday. Among other things, this means:

Testing For Lightning:

• Test receiving email invitations from other clients and adding them to a Lightning calendar
• Test importing and exporting Lightning calendars to/from other calendar applications
• Test how Sunbird works with published calendars that were generated from other applications
• Test how Lightning works with WCAP data from Sun WCAP servers (requires Lightning WCAP extension)
• Are there other interoperability tests you can dream up for Lightning?

Testing For Sunbird:

• Test importing and exporting Sunbird calendars to/from other calendar applications
• Test how Sunbird works with published calendars that were generated from other applications
• Are there other interoperability tests you can dream up for Sunbird?

Since we need the ability to test against as many other calendar applications and calendar servers as possible, we need your help.

Each of us has access to certain clients that others may not have access to. So, any test you can think up that measures the interoperability of your specific calendar servers and clients with Sunbird/Lightning will be appreciated.

Once again, our friends at Linpro AS (http://www.linpro.no) will be sponsoring the prizes for this test day.

Hope to see you in #calendar-qa on Tuesday, October 17. For more information on the test day, please see: http://wiki.mozilla.org/Calendar:Current_QA_TestDay

Thanks for the help!

Posted by Joey Minta at 10:45 AM | Permalink | Comments (18)

Last week's Calendar Test Day was another great success. It was held in
preparation for the 0.3 release. At that time we found 1 new show
stopper bug (which was addressed in 0.3), 5 other bugs (all minor). We
verified several of the fixes that went into 0.3, and we ran over 150
tests in Litmus.

We'd like to thank everyone that helped out: jminta, lilmatt, dmose,
celina63, xFallenAngel, Mc, bbbrowning, karora, mschroder, rogerk, sebo,
lonelybob, nightrat, taliesin, ssitter, omar_public, matthaeus123,
excessory, tedbullock, worzel, and damian.

We would also like to extend a special note of thanks to the good people
at Linpro AS (http://www.linpro.no) for sponsoring our prizes. They have
graciously offered to sponsor the next test day's prizes as well.

Speaking of prizes, they went out to our two winners:
Sebo - took first place with his show stopper defect.
Karora - took second place by running 45 Litmus testcases.

Thanks very much to everyone. I hope to see you all again. Our next test
day will be October 17, next Tuesday. Stay tuned for more details.

-- Clint

Posted by Dan Mosedale at 3:58 PM | Permalink | Comments (4)

We're having a Test Day to help sort out any kinks in the soon-to-be available Sunbird/Lightning 0.3 Release Candidate 1. Come help us test this release and get it ready to be launched. Everyone is welcome to participate, even if you've never been involved with a Mozilla Test Day before.

The test day will go from 0000UTC Oct 3 to 0000UTC Oct 4. Please join us in #calendar-qa on that day and let's get this release finished!

For more details on the test day, please see: http://wiki.mozilla.org/Calendar:Current_QA_TestDay

If you have questions, please feel free to find us in #calendar-qa and we'll be happy to help you.
Hope to see you on Oct. 3!

Clint
IRC: ctalbert

Posted by Dan Mosedale at 3:48 PM | Permalink

Last week, the calendar QA team held their first ever Test Day. It went very very well. Together we ran 661 tests in Litmus, found 16 bugs, and of those, managed to discover 3 new Blocking Defects. Everyone got involved, marcia took care of our prizes; LisaH did our publicity; Johannes and xFallenAngel sorted out Litmus testcases, Sebo set up a public CalDav server for testing; dmose, jminta, lilmatt, and ssitter moderated the calendar-qa channel.

Thanks also to everyone else who got involved: adreas, atrogu, cpm, demo-n, mschroder, rogerk, SirBlackheart, Vali_Systm, VenomousGecko, Vamplr3, Taleisin, LonelyBob, karnesky, ahz, jeizer_a, tbodner, excessory, Damian, bbbrowning, torusturtle, and celina63. We couldn't have done it without you.

And now, the moment you've been waiting for......our winners!

* Karneskey takes prize #1 for most tests run with a whopping 278 tests run in Litmus!
* Sebo takes prize #2 for best defects found with his three defects, and tireless work to confirm two of our blockers!

Congratulations to everyone!

Our next test day will be an informal one, on Tuesday, September 5th. We are currently planning our next big Calendar Test Day, stop by our weekly QA Chat for more information (Thursdays, 16:30 UTC, in #calendar-qa).

Thanks again for all your hard work,
Clint

Posted by Dan Mosedale at 4:41 PM | Permalink | Comments (3)

Posted by Joey Minta at 9:43 AM | Permalink | Comments (7) | TrackBacks (1)

Thanks to everyone that helped out with the test writing day! Many thanks to our moderators jminta, lilmatt, and dmose. Thanks to marcia for the prizes, and to lisaH for our publicity. Special thanks to QA lead ctalbert for all of the organizational work behind this day.

And most of all, a huge thank you to all the people that came through the #calendar-qa channel and helped out. We never could have done it without you.

And now, the moment you've all been waiting for....we have 91 new testcases for the calendar project! Tbodner takes first place with 23 test cases. xFallenAngel takes second right behind him with 19.

We would also like to thank all our other top testers: LonelyBob, Excessory, Darkhack, Celina63, Sishgupta, TorusTurtle, Pcpgomes, Ehwaz, and Taliesin.

All results and full stats will be available at the wiki page

Thanks again to everyone involved for making this event an incredible success. I hope to see you all back for our upcoming Calendar Community Test Day on the 22nd. Watch this blog for more details about that.

Posted by Joey Minta at 8:05 PM | Permalink | Comments (2)

We're off to a great start, with some awesome contributors already writing lots of great testcases. So, if you haven't already done so, head over to the wiki page for all the details. Help us make the Lightning/Sunbird Quality Assurance story as solid as it can be!

Update: Due to the overwhelming response (you guys rock!), we're extending the testcase-writing day for another 24hrs. Note that because the lead developers do need to sleep, there may not always be someone in #calendar-qa immediately ready to answer your questions, but we'll be as responsive as possible.

Posted by Joey Minta at 7:59 AM | Permalink

Thanks in large part to intern-extraordinaire Zach, Mozilla has this great testing tool called Litmus. Up until now, it has served as a testing vehicle for Firefox and Thunderbird nightly bulds. We're now ready to leverage this tool for Sunbird and Lightning as well. First, we need a solid set of testcases that people can run to ensure that the programs are running as they should. This is where you come in!

We want all interested members of our community to help out by writing testcases. No experience is necessary to write testcases, and Clint has done a fantastic job of setting up a wiki-page with everything you need to know to get started contributing Calendar's Litmus area. This Tuesday, we're going to have test-writing day where we're going to have people available to help with any problems, and to get tests that you write into Litmus right away. We also promise to have a small prize for the person who writes the most testcases that day.

For more info on how to get involved, read the wiki-page

See also Clint's newsgroup post.

Please post questions or feedback here, as comments to this post.

Posted by Joey Minta at 2:32 PM | Permalink | Comments (4)

• Bug 307501: Fixes for strict warning (js doesn't trust us)
• Bug 320266: Moves javascript bits that don't implement nsIModule out of components directory
• Bug 327912: Clean up Sunbird context menu
• Bug 341522: Attendees attribute does not work for proxied items
• Bug 343836: Day/Week View: All day events shown on wrong day or twice
• Bug 343968: Events disappeared from unifinder when sort by start date
• Bug 344442: openWalletPasswordDialog and checkWallet are not used
• Bug 345444: Includes missing js file in windows builds
• Bug 344452: Don't add universal style rules for calendars and categories
• Bug 344561: Day/Week view: Header boxes are misaligned if scrollbars are shown
• Bug 344602: Moves Lightning strings to /m/cal/locales
• Bug 345348: Tasks appear in calendar view when progress is modified
• Bug 345490: Wires up Page Setup menu
• Bug 345491: Editing recurring event shows 'All' vs. 'This occurrence' dialog twice
• Bug 345593: Can not modify existing event
• Bug 345606: Print dialog broken [Error: getCompositeCalendar is not defined]

Posted by Simon Paquet at 8:06 AM | Permalink | Comments (11)

1. Bug 157274: Tasks should be displayed in day/week views too
2. Bug 248795: Menu item 'Refresh Remote Calendars' should be disabled when there are no remote calendars
3. Bug 268621: Page Up and Page Down scroll the main view even if focus is not there
4. Bug 278117: Add accesskey for Lightning extension
5. Bug 291220: Redo should use the returned event, not the original event
6. Bug 306079: Create a proper prefs file, rather than initializing prefs from .properties
7. Bug 314927: Make install does not put default.xpm into $(DESTDIR)$(mozappdir)/chrome/icons/default
8. Bug 328197: Calculate the duration of todos correctly
9. Bug 329642: Remove global delete listener to make cancel dialog always work
10. Bug 330391: Add tooltips to Lightning
11. Bug 330573: Added TZID information to EXDATE attribute
12. Bug 331026: Start with correct setting in customize toolbar menulist
13. Bug 333923: Converts Sunbird preferences from xpfe to toolkit
14. Bug 335793: Don't keep 100% complete when changing task status
15. Bug 338475: Updates paths in installer
16. Bug 338957: Paste doesn't work when in the day/week views
17. Bug 339083: Copy/Paste meeting-request stopped working
18. Bug 339260: ns_not_implemented should be ns_error_not_implemented
19. Bug 339321: Disables preprocessing for PNGs
20. Bug 339639: Renames poorly named css selectors
21. Bug 339714: Add setup.exe target to Sunbird's NSIS installer makefile
22. Bug 339986: Update Sunbird to use toolkit's packager.mk for Universal Binary support
23. Bug 340414: Add 'View workdays only' and 'View tasks in view' toggles to Lightning
24. Bug 340559: Moves sunbird configure's default build options into configure.in
25. Bug 340723: Encapsulates ifdefs in comments to make a valid dtd
26. Bug 340831: Switching views leaves phantom all-day events
27. Bug 340971: Cleans up makefiles, etc. to allow for building langpacks
28. Bug 340984: Strict warnings in calItemBase.js and calAlarmService.js
29. Bug 341154: Added calIIcalProperty::icalString attribute
30. Bug 341403: Make error if build with --enable-installer on Windows
31. Bug 341518: View navigation buttons move when changing views
32. Bug 341580: Errors when adding/modifying/deleting tasks
33. Bug 341688: Tasks without due dates mess up month view
34. Bug 342098: Refactor startup in extensions.js so that showView will only ever be called once (Sunbird pref patch)
35. Bug 342165: Removes css from winstripe
36. Bug 342407: Freshen installer to new NSIS code
37. Bug 342568: Removes 'today' attribute when reusing day boxes in week view

Posted by Simon Paquet at 3:06 AM | Permalink | Comments (13)

• Bug 339670: Fix SQL query for non-recurrent events being incorrect when getItems was called for a range of time with different start and end offsets
• Bug 335594: Makes Sunbird's release notes url NOT hardcoded
• Bug 337848: Only use times for Today and Tomorrow in the agenda view
• Bug 339509: Day view doesn't always display the correct day
• Bug 339509: Wrong day selected in views if selected timezone does not match system timezone
• Bug 315960: Improve performance when switch day/week views
• Bug 335643: Make tasks in the multiweek and month views show up even if their start date is earlier than the start of the view

Posted by Simon Paquet at 5:57 AM | Permalink | Comments (11)

• Bug 239431: Allow choosing multiple exceptions more easily
• Bug 329225: Moving views should also move minimonth
• Bug 333372: Week number for multiweek view is off when Sunday is not the start of the week
• Bug 334076: Agenda tree only shows the events from the calendars in the composite at startup
• Bug 338311: remove unneeded files from Add-ons Manager migration
• Bug 338432: Sunbird doesn't require xpcom_obsolete

Posted by Simon Paquet at 8:25 AM | Permalink | Comments (14)

This week has been another busy week for the Calendar Squad. In addition to the general calendar meeting this week (notes here), we also had a separate meeting for Sunbird 0.3a2 release planning. The end result of this meeting was the identification of 3 specific goals for the upcoming release:

• Sunbird 0.3a2 should have no internal dataloss
• Sunbird 0.3a2 should fully utilize the new-views code.
• Sunbird 0.3a2 should have no major regressions from 0.3a1.

As a result of these goals, we did a bit of re-triaging of blockers for 0.3a2, and this current list should be pretty close to final.

Additionally, the following bugs have had fixes checked in since the last status update.

• Bug 325477: (Both) Begin implementing an undo/redo system for Lightning, fix places where Sunbird's undo/redo system should be used, but isn't
• Bug 331887: (Both) Make the 'Choose Calendar' dialog for import/export resizable
• Bug 330385: (Lightning) 'My Timezone' preference isn't selected when the prefpane loads
• Bug 329669: (Both) Views don't update after changing timezone setting - restart required
• Bug 327856: (Both) Views don't display 0-length events
• Bug 266241: (Lightning) Regression fix for previous checkin in this bug.
• Bug 331814: (Both) Convert event dialog's task percent complete from menulist to textbox with error handling.
• Bug 332037: (Both) Make Sunbird built with MOZ_DEBUG=1 be more obvious.
• Bug 331997: (Both) Edit Task dialog does not update task completed status correctly.
• Bug 326813: (Both) Day/week view: left click on event does should select day too
• Bug 332311: (Lightning) Also apply new winstripe higher contrast buttons to lightning
• Bug 323288: (Sunbird) (Mac only) Makes Sunbird not use Camino's creator code.
• Bug 325650: (Lightning) Performance fix for tree-refreshing when editing/adding/deleting calendars
• Bug 329737: (Both) Invalid alarms should just report an error, but not stop parsing
• Bug 301748: (Both) calIFileType isn't l10n friendly
• Bug 329571: (Both) Error when setting composite calendar's default calendar with usePref==true
• Bug 332268: (Both) Editing start date of all day events adds extra day to end date
• Bug 332270: (Both) Fixes for js-strict warnings
• Bug 326562: (Both) No 'Visit URL' button in the new event dialog
• Bug 322768: (Sunbird) Remove dateUtils.js in favor of calIDateTimeFormatter
• Bug 332265: (Sunbird) 'All' vs. 'This occurrence' selection ignored when deleting recurring event via keyboard.
• Bug 331796: (Both) The recurrence dialog should use dateFormat.properties (reduce l10n workload
• Bug 332443: (Both) In weekview, dragging an item to a different day and different time ends up at the wrong time

Posted by Joey Minta at 6:12 PM | Permalink | Comments (1)

As of a few hours ago, we were informed that the Windows tinderbox (solaria) had finally come back online. As of the writing of this entry, it had successfully built and dropped a fresh copy of Sunbird with all of the changes mentioned in the previous Status Update, and a few others that have landed since then. Expect a Lightning build to drop soon as well. Huge thanks go out to everyone who put in time on this!

Given that we've had a smaller number of eyes on the builds lately, I'd like to ask everyone to test these Windows builds a bit more thoroughly than usual and to please file good bugs if you notice any problems.

Now for the bad news: The Mac tinderbox (hilo) is now on fire and needs to be upgraded. :-(

Posted by Joey Minta at 4:15 PM | Permalink | Comments (5)

• Bug 325068: (Sunbird) Improve UI for selecting print options. Make printing pluggable
• Bug 328073: (Both) Monthly recurrence doesn't work well.
• Bug 330020: (Both) Regression fix: View navigation buttons don't work
• Bug 328986: (Lightning) Update maxVersion to handle new TB/FF version numbers
• Bug 325519: (Both) Give names to error codes when reporting them to users.
• Bug 330244: (Both) Replace deprecated preventBubble() calls with stopPropagation().
• Bug 325726: (Both) Update several internal observers that are missing needed methods.
• Bug 325068: (Sunbird) Improve UI for selecting print options. Make printing pluggable
• Bug 329347: (Lightning) Remove extra debugging code
• Bug 321608: (Both) First day of the week setting not honored in Multiweek/Month views
• Bug 321560: (Sunbird) Wrong day selected in views when using the minimonth or Go To Day, for some timezones
• Bug 327662: (Sunbird) 'Currently Selected Day' filter in the unifinder doens't update when a new day is selected
• Bug 329415: (Both) Disable the 'Remove exception' button when no exception is selected in the dialog.
• Bug 329360: (Both) Fixes for javascript strict warnings
• Bug 266241: (Both) use system time format in the views as well
• Bug 329654: (Both) calDateTimeFormatter always uses selfmade long formatted date string hack
• Bug 330140: (Both) Disable going back after the calendar was really created.
• Bug 321693: (Sunbird) Listen for changes to the multiweek weeks-in-view preference and update the view accordingly
• Bug 330103: (Both) Removed hard-coded strings to allow for localization
• Bug 327805: (Both) Use calendar name as initial filename during calendar export.
• Bug 325519: (Both) Add specific errors for most common failures, along with brief strings describing them
• Bug 329855: (Lightning) Add support for default alarm options in new events/tasks
• Bug 322958: (Both) caldav time-range needs to be UTC datetimes, not dates
• Bug 327832: (Both) 'To' date and time no longer linked to 'From' date/time, in new event dialog
• Bug 321380: (Sunbird) Can't remove days off from multiweek/month views
• Bug 329226: (Both) Highlight 'today' in the views and the minimonth
• Bug 331698: (Both) Minor view fix to allow for easier theming
• Bug 329581: (Sunbird) (Mac only) hiddenWindow throws errors about obsolete overlays
• Bug 331022: (Both) Shared use of 'none' for both Status and Priority causes localization trouble in some languages
• Bug 331737: (Sunbird) (Mac only) 'About' menu-option should only be available under Window, not Help
• Bug 323696: (Both) Dragging events that span multiple days results in unexpected behavior
• Bug 329975: (Both) Edit Task dialog always shows 0% complete
• Bug 263479: (Both) Tasks aren't removed from month/multiweek views when deleted
• Bug 331701: (Sunbird) Events created by drag'n'drop should be placed in the selected calendar, not always the 1st calendar
• Bug 331485: (Both) When creating tasks with default alarms, the task is always set to today, not the selected day
• Bug 324676: (Both) Day/week view don't refresh correctly when default start/end hour preference is changed

There are also several other bugs that will likely land in the next few hours, but I'll just report those in the next status update. As usual, thanks go out to the entire calendar team for there hard work, and of course to the entire community for testing and filing good bugs!

Posted by Joey Minta at 11:45 AM | Permalink | Comments (5)

Posted by Joey Minta at 4:09 PM | Permalink | Comments (3)

With this status update, I thought I'd try to give you some insight into what went on in preparation for the Lightning 0,1 release candidates.

As the blocking list grew smaller, it appeared that March 4 could be the date for Lightning 0.1RC1. (As you know, this didn't happen, see below.) In the week prior to that, many small, low risk bugs were identified and patched. Examining these bugs you'll notice that a majority of the patches were just a few lines long. There were also a fair number of changes to recurring events, to enable individual elements of recurring series to be edited.

• Bug 323093: (Both) Week/Day view should expand when events fall outside the default hours
• Bug 328084: (Both) Errors/unexpected behavior when mixing 'Modify this occurrence' and 'Modify all occurrences'
• Bug 328653: (Both) Alarms set for 15 or 30 min after an event show up as 15/30 minutes before.
• Bug 328761: (Both) Alarms greater than 9 hours in advance end up at random times.
• Bug 328763: (Both) Alarms for all day events rounded up to the nearest midnight
• Bug 328508: (Both) JavaScript error when dismissing the last alarm.
• Bug 328632: (Both) Times displayed in alarms are ugly and include useless timezone information
• Bug 328483: (Lightning) 'Play sound' preference when alarms are fired does not work
• Bug 328510: (Both) Deleted exceptions to recurring events remain in data-storage, but should be purged
• Bug 328011: (Both) Create easier method for determining whether 2 occurrences are equal
• Bug 325786: (Both) No way to add exceptions to events in the event dialog
• Bug 328011: (Both) Audit code for proper use of identify testing of XPCOM objects and fix violations
• Bug 329240: (Both) Fix regression from Bug 328011
• Bug 327845: (Both) Error writing items with attendees to local (storage) calendars
• Bug 327877: (Both) Multiple entries for same task are created in agenda when editing task.
• Bug 328754: (Sunbird) Cannot create new events if default alarm for events is 'On'
• Bug 326352: (Lightning) Bump version number to 0.1

• Bug 328597: (Lightning) Calendars are not removed from the list immediately upon delete
• Bug 329373: (Lightning) Creating an ICS (webdav) calendar with a file:// url can fail.
• Bug 326116: (Both) Don't download an ICS (webdav) calendar if eTags are present and indicate the file has not changed
• Bug 315511: (Both) New ICS (webdav) calendars are sometimes marked read-only on creation
• Bug 329486: (Lightning) Agenda view's displayed times aren't always in the correct timezone.

At this point, the MozStorage problems were fixed and when things tested nicely with the next set of nightly builds, we had Lightning 0.1RC1

It didn't take long before we found at least one more bug that we wanted to fix before releasing the final version of Lightning 0.1. In the end, 2 bugs were fixed between RC1 and RC2.

• Bug 329647: (Lightning) Agenda view sorts events based on their time in Los Angeles, should work off local time.
• Bug 329800: (Lightning) Agenda view puts events starting at Midnight, and all day events, in the wrong day

And that brought us to the current state, Lightning 0.1RC2. At the time of this writing, there have yet to be any bugs filed that would stop RC2 from becoming the final Lightning 0.1. Again, immense thanks goes out to everyone who has helped us test and provided feedback concerning these release candidates.

Posted by Joey Minta at 6:40 AM | Permalink | Comments (2)

This post is directed at anyone who is using/testing nightly builds of Sunbird or Lightning.

In the next half-hour, I'm going to be landing an over-haul of the alarm system. For those of you who want the gory details (or who want to see how much work reviewing a patch truly takes), please read Bug 315051. This overhaul is intended to solve, among other things, the following problems:

• Alarms missed while Sunbird/Lightning was closed are not fired when the program is started up.
• Alarms for ics files do not meet RFC-2445
• Alarms for recurring events do not work
• Alarms scheduled more than 6 hours in advance of an event are not fired

In order to make these changes, however, significant changes were needed in a broad range of code areas, including, most critically, the sqlite database. While every effort has been made to ensure that the database upgrade necessary will happen automatically and without any problems, users should back up their profile before using tomorrow's nightly Also, users should note that using older builds after upgrading may result in dataloss.

How you can help:

The new alarm code currently contains additional debugging code to help get feedback on the effectiveness of the changes prior to the release of Lightning 0.1. The vast majority of this feedback will be provided in the form of console output. Therefore, if you are testing alarms, it is recommended that you run Sunbird or Thunderbird+Lightning with the -console command. The -console command is a commandline argument. These arguments are described in more details here.

Things to look for

• When starting an updated build of Lightning/Sunbird that previously used the old alarm code, you should notice an output that looks like:
  *** Calendar schema version is: 4
  **** Upgrading schema from 4 -> 5
  Starting calendar alarm service
• All of your past alarms will fire the first time you run an updated build. Click 'Dismiss All' to get rid of them*
• Whenever Lightning/Sunbird starts up, it will output to the console exactly what it is doing for each alarm that it finds. This includes things like "The alarm has been previously acknowledged." or "This alarm is too far in the future." or "This alarm is in the past and has not been acknowledged. Firing now." If you find alarms misbehaving, posting this information in a bug report will be extremely helpful

*Note: I rather expect there will be issues with firing multiple alarms at the same time. This, however, was beyond the scope of the current bug.

Posted by Joey Minta at 2:31 PM | Permalink | Comments (1)

The following bugs have had fixes checked in since the last status update. Additionally, a substantial amount of code-restructuring was done that included removing obsolete files from the CVS repository as well as beginning our migration towards a better localization structure.

• Bug 324849 - (Both) Check to see if a remote calendar has been modified before uploading changes
• Bug 295387 - (Both) Day/Week views do not show all-day events
• Bug 326003 - (Both) Localization restructuring
• Bug 324665 - (Lightning) New events do not appear until the view has been refreshed.
• Bug 319790 - (Both) Add a way to calculate a week-number from a date. (Fixes the 'Week 0' bug)
• Bug 312830 - (Both) Add a scrollbar in the month-view for when more events are present than can be shown
• Bug 325459 - (Both) Month view's relayout can occassionally fail
• Bug 323776 - (Lightning) Make sure Lightning only installs in the versions of Thunderbird it was designed for
• Bug 326335 - (Lightning) Deleted calendars don't disappear from the list until it is refreshed
• Bug 325592 - (Sunbird) Fix build problems on the MOZILLA_1_8 branch
• Bug 326268 - (Sunbird) Use the new week-number calculation service in the multiweek view too
• Bug 326390 - (Both) Completed dates for tasks are not saved
• Bug 326331 - (Both) For new events, the event-dialog should default to the selected calendar, not the first one
• Bug 304084 - (Both) All day event gets changed to previous day when editing
• Bug 326653 - (Lightning) Can't select all day events in week/day view
• Bug 326287 - (Both) Change default event background to a lighter, easier to read color
• Bug 326787 - (Both) Events spanning multiple days can sometimes mess up the day/week view
• Bug 321693 - (Sunbird) 'Number of Weeks' option for the multiweek view is always disabled
• Bug 326794 - (Sunbird) Localization restructuring
• Bug 320869 - (Sunbird) CVS restructuring
• Bug 322060 - (Sunbird) The first day in the multiweek view should show the month as well
• Bug 321560 - (Sunbird) For people east of GMT, the wrong day is selected when using the minimonth
• Bug 325701 - (Both) Do not display a time for all day events in the month/multiweek views
• Bug 326439 - (Lightning) make the default calendar name ('Home') localizable
• Bug 298373 - (Both) Prompt users before deleting a calendar
• Bug 326132 - (Both) For users east fo GMT, all-day events sometime falsely trigger a 'Start time after end time' warning.
• Bug 321383 - (Sunbird) Multiweek view boxes appear in weird colors.
• Bug 322059 - (Both) Current year not visible in month view.

Thanks again to all of our testers and bug reporters, as well as to everyone who submitted patches for these bugs. Keep up the good work!

Posted by Joey Minta at 12:08 PM | Permalink | Comments (11)

• Bug 319701 - (Both) Move Lightning to the decorated views and tidy up some flex/resizing issues
• Bug 321898 - (Both) Right-clicking on minimonth also displays dropdowns instead of just context menus
• Bug 293192 - (Lightning) Make sure clicking on a folder in the tree always returns to mail-view
• Bug 322230 - (Both) Add a service to return datetimes into various 'pretty' formats
• Bug 322272 - (Both) Disable the R button until view rotation works better
• Bug 322859 - (Both) 'Organizer' property lost when items are cloned/edited
• Bug 281935 - (Sunbird) First step towards a better localized build story
• Bug 322095 - (Sunbird) Allow selection of single instances of repeating events
• Bug 306692 - (Sunbird) 'Open calendar file' does nothing.
• Bug 323057 - (Both) Fix javascript warnings in the new views
• Bug 321563 - (Both) Day and week view don't always show early events

Posted by Joey Minta at 4:00 PM | Permalink | Comments (9)

• Bug 320823 - (Sunbird) Missing preference makes themes unusuable
• Bug 297934 - (Sunbird) Make Sunbird use the new views
• Bug 306188 - (Sunbird) Task list context menu options disappear when first clicking the minimonth
• Bug 315719 - (Both) Events with neither DTEND nor DURATION handled incorrectly (end-date shows as 1 Jan 1970)
• Bug 315960 - (Both) Improve performance times for redrawing/moving the (new) month/multiweek views
• Bug 315962 - (Lightning) No icons shown for Lightning buttons in TB's Customize Toolbar window
• Bug 298352 - (Lightning) Allow users to specify the first day of the week in preferences

• Bug 321413 - 'Extensions' and 'Themes' windows do not show up due to extraneous debugging code
• Bug 321375 - Context menus for the views do not appear.
• Bug 321535 - Right clicking and selecting 'New Event' doesn't always give the right default date.
• Bug 321378 - JavaScript error when adding/modifying an event before all views have been shown.
• Bug 315955 - The Month/Multiweek views display the incorrect times for events (also a Lightning 0.1 blocker)

It's probably also important to point out that the landing of the new views simultaneously fixed a large number of outstanding bugs. Searching for all of these bugs is somewhat difficult, but this list should give you a good idea of them.

There are still currently 18 identified regressions from the new views landing (6 of these have patches awaiting review). This list of bugs can be viewed here. Additionally, the following regression has appeared in Sunbird since 0.3a1 was released:

• Bug 320266 - Many "Failed to load XPCOM Component:" info bubbles in the js-console when starting a new profile.

Posted by Joey Minta at 7:52 AM | Permalink | Comments (2)

Those of you that have been following Sunbird development closely have probably heard some mention of the 'new views'. This refers to a set of xml files that create a new set of day/week and month views. Lightning has already been using these files, but in order to make them usable in Sunbird substantial changes needed to be made to the current codebase. The entire team has been putting in a lot of work on Bug 297934 in order to accomplish this. This afternoon, they landed.

We need your help

These changes were far too big to do perfectly. Tomorrow's build, which will include the new views, will be very buggy. Many of the bugs have already been anticipated and filed. However, many others likely remain unknown. Those interested in testing these new views can help out greatly by providing specific, reproducable bug reports. Please do NOT comment about the regressions in the new-views bug. We are tracking all of the regressions from this landing in Bug 321164. If you find another regression, please file the bug and make it block this tracking bug.

New hackers

With the landing of these new views, now might be a good time for anyone who has considered trying their hand at hacking calendar code to jump in. Some of the regressions created by this bug will be rather difficult, but others will make for very good first bugs. Those interested in helping out may find the following (works-in-progress) pages useful:

• Beginner's Guide to Hacking Sunbird/Lightning
• Draft Developer's Guide

Please be patient with us as we try to iron out all the problems from this landing. In the end, it should make your Sunbird experience much better. For instance, the day and week views already offer one of the most requested features, inline-editing. Also, in these views, dragging and dropping is back. Landing these views also allows the Lightning and Sunbird development processes to be much more united, so hopefully they will move more quickly.

Happy testing and Happy Holidays!

Posted by Joey Minta at 2:02 PM | Permalink