We’re back! The entire OSAF/Chandler world was offline for about 24 hours from April 27th at 2pm to April 28th. This outage has been fixed with no permanent damage.

The root cause was “sparking” (ouch) on the power lines reported by PG&E.  Our colo hosts, Hosted @ ISC, switched over to their generator as a precaution but the generator failed.  ISC started shutting down machines when they knew the outage would exceed their UPS power.

Here’s where our outage stretched out longer than it needed to. ISC didn’t let us know they were powering down the machines, or that power was back up a couple hours later. They responded to my 3pm inquiry to their ticketing system late on the 27th, saying that everything should have been fine hours ago. Unfortunately, I had already gone to bed, so the OSAF/Chandler outage had to wait out the night.

In the morning of the 28th, I asked ISC to hit the power buttons on the machines for me, but nothing happened. I packed up quick tech kit plus some spare machines and hopped in the car for the hour drive to Redwood City. On-site around noon, I confirmed the machines appeared dead. Weird. Hopefully the power issues hadn’t killed all 4 physical machines’ power supplies or motherboards at once, right?

Turns out, our managed power device that lets us turn machines on and off remotely had taken a header. I started moving machines’ power around, finding out by the end which ports on the power switch were dead. The Hub machine moved off the power switch entirely.

That would have all be relatively simple, except for the extended duration, but there were other post-shutdown details that smacked me around for a while. I found that the tightened DNS configuration implemented back when DNS security went crazy kept our DNS machines from answering questions from themselves. I kept production machines like Hub off until I had DNS sorted out.

But far worse was a surprise related to the Debian Etch to Lenny upgrade. Since Lenny was released a few months ago, I’ve been upgrading OSAF machines in the background. I don’t know how I missed this, but the upgrade can remove the package used to bring up networking (ifupdown). I had been breaking the cardinal sysadmin rule of always rebooting machines after upgrading the OS, so I was very very confused when some machines came back up without any networking. Including our primary DNS server. And the secondary DNS server seemed broken because of the DNS config error I mentioned above.

I shot myself in the foot even more because before I realized all this, I had decided that the already-extended outage “seemed a good time” to upgrade the Hub from etch to lenny. After the reboot, no networking! Gah, it was just working fine before the upgrade!

So, after getting a grip on what was going on, tracing through networking startup scripts, and tracking down the missing ifupdown package issue, I go bumming through the ISC office for a USB key. I use one of the existing machines to pull the ifupdown package (both i386 for the virtual machines and amd64 for the Hub) using a command-line web browser, troll through syslog to figure out what device to mount, and get these packages onto their needed machines. Luckily, this all works and all machines come back up.

All’s well that ends well I suppose, but this was a tough outage to swallow after the 9 hours from the big fiber cut less than a month ago. Natural questions like “is our hosting good enough?” and “should we move?” come up.

My view is that weird things happen in every hosting environment; moving is not a cure-all for reliability issues. Our reliability isn’t as good as we’d like or as good as could be achieved, but I feel it’s still better to sit tight. The main reason is cost: hosting the Hub consumes a good amount of bandwidth (about 8Mbps) and ISC is providing all services (space, power, bandwidth, remote hands) for free for 9 rack units worth of equipment. It would be possible to move some services like mailing lists, code repositories, and wikis to other free services and someday the community may choose to go that route.  But it’s nice to not have restrictions on capabilities or capacity that we get from hosting almost all of our own services; many open source projects would love to have access to the resources and flexibility that OSAF enjoys.

Overall I think we’ve just had a spate of bad luck and while a very rare 24-hour outage might be unacceptable to a commercial venture, as long as they stay very rare, they are acceptable to OSAF and Chandler communities and very worth the tradeoffs.

There are three items I want to undertake as a result of the outage:

• Place a DNS secondary outside of ISC
• Print out some phone numbers, IP ranges, and other “might need it offline” info
• Talk to ISC about coordinating during outages

As a final note, it turns out I could have determined that “everything should be fine now” by going to status.isc.org where there was some information about the outage, including when it ended. I hadn’t been checking that page during the outage but I certainly will (as well as using the phone as needed) during any future outages.

On Wednesday Nov 12th, our final OSAF/Chandler Project servers will migrate to ISC.  The affected services include chandlerproject.org web and wiki, subversion, and downloads.  Mail and Chandler Hub will not be affected.  Overall downtime should be from about 1pm Pacific to about 4pm.
Your patience is appreciated.  Please report any problems you have after the outage to the chandler-users mailing list and IRC channel.

On Wednesday Nov 5th, I’ll be moving two OSAF/Chandler Project servers to our good friends at Hosted @ ISC.  The affected services include Chandler Hub, OSAF mail (such as mailing lists), and the iGoogle widget.  These servers will be on ISC’s gigabit connectivity and large UPSes so we’ll continue to get great infrastructure and ability to grow (particularly in bandwidth costs related to Chandler Hub usage) for free.  This is hugely important for our mission of delivering free and open productivity tools for groups.  Our thanks to ISC for their ongoing support, going on 8 years now.

The outage will last from about 9am to perhaps 2pm or so.  There won’t be any changes other than moving cities and IP addresses, but there may continue to be small problems after that that get fixed over a couple days.  Your patience is appreciated.  Please report any problems you have after the outage to the chandler-users mailing list and IRC channel.

The Chandler Project is pleased to announce the 1.1.0 release of Chandler Server (Cosmo)!

Chandler Server is a server and Ajax web UI for managing and sharing calendars, events, and tasks. It implements open data standards including CalDAV, WebDAV, Atom, and Atompub.

This release contains two significant features and four bug fixes. Any user can now delete their own account and data by using the settings dialog. Interoperability with some CalDAV implementations including iCal 3 should be improved by support for the CTAG draft standard.

The Chandler Hub has been updated and is now running the 1.1.0 version as well.

Chandler Server 1.1.0 is available for download as a ready-to-run bundle at:

http://chandlerproject.org/serverdownload

and the source code is available from subversion at:

http://svn.osafoundation.org/server/cosmo/tags/rel_1.1.0

Send us feedback at the open mailing list (no subscription required):

chandler-users@osafoundation.org

We look forward to hearing from you!

The issues fixed in this release include:

• [Bug 12283] Users should be able to delete their own Hub accounts
• [Bug 12279] Add support for CTag, Apple’s extension of ETag to a Calendar Collection
• [Bug 11851] Sort triage status by TriageStatusChangedDate
• [Bug 12334] Fix recovery pages
• [Bug 12349] In IE7, in DV, long notes obscure DV header section
• [Bug 12357] Account browser help link broken

The Chandler Project is pleased to announce the 0.7.5 release of Chandler Desktop!

The Chandler Project is an open source, standards-based information manager designed for personal use and small group collaboration.

The 0.7.5 release of Chandler Desktop simplifies the Chandler UI by changing elements confusing to new users. In particular, multiple toolbar buttons were removed, “tasks” were replaced with “starred items”, the “triage” button was renamed to “clean up”, and the items created when first starting have been made more useful. The sidebar list of collections can now be reordered by dragging them in-place. A variety of build/packaging and platform-specific bugs have also been fixed.

Additionally, Chandler Desktop has updated its sharing protocol to match that of Chandler Server (Cosmo) 0.13. Previously, a user could republish items that had been shared to them read-only to obtain read-write permission to those items. See here and here for more information. People using versions of Chandler Desktop prior to 0.7.5 will not be able to republish items to recent versions of Chandler Server including Chandler Hub.

A list of known issues in this release is at the bottom of this announcement.

Chandler Desktop 0.7.5 is available for download for Windows, Mac, and Linux at:

http://chandlerproject.org/download

Additional information is available from the Chandler Project homepage.

The bugs fixed in this release include:

• #5058 Add the ability to reorder collections in the sidebar
• #7024 Improvements to divider in the sidebar
• #10785 Tab key press doesn’t end lozenge edit on Ubuntu
• #10997 Bad dependency on tools/ dir
• #11013 Plug read-only security hole
• #11238 Reminder popup prevents to use Chandler
• #11239 Using delete via context menu deletes wrong user item - no indication to user
• #11290 Rename Triage button
• #11429 Re-organize the File menu
• #11676 Added a new collection on the hub & Chandler desktop hung
• #11678 make the links in the ‘Tip of the day’ clickable
• #11684 Add “Show Tips” to the Help menu
• #11689 Chandler crashed on linux with X window System error
• #11705 Need to be able to tell if a reflist attribute has been deleted or not
• #11712 Full Name not showing up for sender in email I receive in Apple Mail
• #11729 Generate items from dialog
• #11770 Strip down UI
• #11771 Change task stamp to star stamp
• #11772 Fill-in OOTB items
• #11783 Traceback when making ‘Future’ edit on recurring series
• #11814 Change hint text in quick entry bar to: Create a new note
• #11819 Leopard Desktop releases show “Python” not “Chandler” for name
• #11823 Couldn’t migrate 0.7.3 to 0.7.4 on MacOSX
• #11830 SAST timezone missing
• #11831 German translation’s key-bindings (at least on Mac) are bad
• #11836 Change Copy URLs to Clipboard text to…
• #11838 Language Switch doesn’t work
• #11880 Disallow adding read-only items to other collections
• #11884 Better sharing error messaging
• #11887 Exception changing visible hours in multiweek (month) view
• #11900 Change View>>Triage to View>>Clean up
• #11903 Traceback after upgrading
• #11911 D-click to mark item as 2-triage statuses away
• #11914 Drags to read-only collections succeed
• #11919 Can’t cancel publishing a collection

There are five known issues with this release we’d like to highlight:

• #11878 Can’t put items you received via Email on the Server
• #11921 Read-write access should override read-only access
• #11946 Crash manipulating particular event in Chandler
• #11947 No highlight state in month view
• #11948 sidebar update oddity when creating a collection

This list of known issues includes an application crash that previously didn’t happen when editing an event in a collection that’s not currently selected. All these issues involved sophisticated sharing scenarios (multiple collections with some read-only and others read-write, and sharing items via email) or are UI oddities with simple workarounds.

Thanks for your interest in Chandler Desktop!

Interoperability is an important part of the Chandler Project vision.

Chandler is about trying to match the way people really work. And everyone uses lots of tools to get their job done. One of the first things people want to know when considering trying out Chandler software is “Will it work with what I already use? Can I switch back if I don’t like it? Will it work with the tools that friends of mine use?”

We believe the answer to all these questions is “YES”! You can safely and productively start using one or more of the Chandler Project components on top of your existing toolset. Go ahead, try it out! Read more below to learn the details.

For a bullet-list summary of our best-available notes on specific applications and which features are supported with each, see our interop overview.

Import/export

The gold standard of calendar transfer is the “ICS” file (in iCalendar format). Most calendar and task list applications support both import and export of ICS files.

You can try out Chandler Desktop without switching from your current setup. Just export one or more ICS files from your current application, then import those files into Chandler Desktop (continuing to use your current app). To switch over permanently, just export+import again a final time!

If you later decide you’d like to change again, you can export ICS files from Chandler Desktop or Chandler Hub, using those files for import into a wide variety of applications.

We’ve seen import and export work for Outlook 2003/2007, Mozilla Lightning/Sunbird, Apple iCal, and others; it should work with a great many apps, probably yours included.

Note that Outlook doesn’t export full information by default; we’ve found this $10 application from littlemachines produces high-quality exports from Outlook that work well with Chandler Desktop.

In practice, doing ICS import/export can have gotachas. Not all application combinations/roundtrips are 100% perfect. We urge you to keep backups and try out import/export before committing your important data to any application. In Chandler Desktop, we’ve spent a lot of time tuning our import/export routines to handle as many variants and details as we can. Chandler Desktop properly handles events, tasks, timezones, recurrence, and other details. Please report any import/export problems you encounter.

We’ve put together some additional information about import/export with Chandler Desktop specifically, so check that for additional hints and notes.

Synchronization

ICS import/export is great for transferring your data between apps, but it’s a manual process not suited to keeping multiple applications in sync. Usually when you import a data set, your app will overwrite changes you may have in your local copies of those events. It’s hard to make changes in two separate apps.

Chandler Desktop and Chandler Hub both support multiple network sync protocols. Where other applications (Outlook, iCal, etc) overlap at least one of these protocols, interoperability is possible on at least some level.

One main idea to keep in mind when thinking about these various systems is whether a scheme is “read-only” or “read-write” (ie, bidirectional). It seems like read-only (or 1-way) interoperability works more reliably today, but protocols like CalDAV promise a new era of real-time, 2-way synchronization of calendar data between lots of free and for-pay applications and web services.

The big news is that you can do 2-way/read-write calendar and task synchronization today, both privately and shared with other people. Here’s a list of the main ways to do that, based on Chandler Project software.

Webcal, 1-way sync

The most simple network protocol is to take an ICS file (see above in import/export) and post it to the web, so various apps can download it (redownloading to check for changes periodically). This system is called webcal.

Chandler Desktop works great for subscribing to a number of public webcal URLs and overlaying them all on one canvas. This is a great way to keep track of lots of calendars.

If you store any events/tasks on Chandler Hub, then you can login to get a URL that you can enter into the right spot in Outlook, Apple iCal, Google Calendar, Lightning/Sunbird, Evolution, Zimbra, and many other apps to synchronize that Hub calendar with your app. This is always a read-only/1-way procedure.

Using webcal, in Outlook 2007, you can overlay say personal or family Hub calendars on top of your Exchange/Outlook calendars you use at work. (Look for “Internet Calendar” features in Outlook’s help.) If you make a change on the Hub or Chandler Desktop and then synchronize, you’ll see that change in your work Outlook’s display.

You can also subscribe to Hub calendars in Outlook 2003, but only view the calendars side-by-side. Other apps like iCal, Lightning/Sunbird, Google Calendar, and Evolution all support overlaying the Hub calendar with other calendars.

Many applications, Outlook included, can also publish a webcal calendar to a web server. You can use Chandler Hub as a destination server for most of these webcal-publishing apps. This works, but please note this does not provide a web UI for that calendar, and it’s again a 1-way publication. The original application will very likely not detect any changes made to this webcal file on the server.

Webcal, 2-way sync

Chandler Desktop can also do 2-way synchronization via webcal. Most applications treat a webcal file as read-only or write-only, but Chandler Desktop will check for changes in a webcal file it is monitoring and integrate those changes. If used with another application that also checks for changes, you get 2-way synchronization. We know Lightning/Sunbird does this (though you might chose to use CalDAV to synchronize instead).

CalDAV, 2-way sync

CalDAV is an emerging standard protocol for open calendar exchange. It’s not a protocol that’s used directly between two clients (like ICS files are), but rather defines a calendar server to which multiple clients can subscribe and synchronize. Chandler Hub also provides a read-write web UI to any calendar you store or use in your account.

The Open Source Applications Foundation via the Chandler Project was an early supporter of CalDAV. Together, our Chandler Desktop application and Chandler Server server product are some of the oldest and most mature implementations of the CalDAV standard and we plan to continue that support.

Chandler Hub is, as far as we know, essentially the leading free CalDAV service offered to the public. Given a fully-cooperating CalDAV client (Lightning/Sunbird, iCal 3.x, and Evolution all cooperate to various degrees), you can use these other clients regularly or occassionally and even use Chandler Desktop for advanced work (like sharing a single item between multiple calendars).

Chandler Desktop can subscribe to and publish a collection (calendar+events) to any CalDAV server (Apple Calendar Server, RSCDS, Bedework), or actually any WebDAV server (Apache mod_dav, .Mac, etc). Both of these mechanisms support bidirectional (read-write) synchronization, so multiple applications or people can all create, edit, and delete events and tasks any time they want, using the application of their choice.

iCal 3 (in Apple 10.5 “Leopard”) is a great new CalDAV-using PIM client. You can use it to make changes to your Hub collection, and still be able to use the Hub web UI to make changes from anywhere. Note that iCal 3 supports read-write calendars only to calendars in your account. Chandler Desktop and Chandler Hub let you subscribe to shared collections owned by other users with full read-write access.

Email integration

Chandler Desktop is not a complete email client; it is rather intended to complement your existing email client. The mechanism we use is to create dedicated Chandler folders on your IMAP server. Using your regular email client (Outlook, Thunderbird, Mail.app, Evolution, etc), you just drag an email from your inbox into a Chandler folder, where the message will be parsed for event, task, and other information.

You should also be able to send email update of items from Chandler Desktop using just about any outgoing mail server available. Events emailed this way appear as ICS attachments. We’ve tested Exchange, Postfix, Gmail, Yahoo mail, and Hotmail/MSN among others.

The Chandler Project is pleased to announce the 0.7.4 release of Chandler Desktop!

Chandler Desktop is an open source, standards-based personal information manager (PIM) built around small group collaboration and a core set of information management workflows modelled on Inbox usage patterns.

The 0.7.4 release adds a Tip of the day feature and a German translation contributed by a user. The triage status behavior was improved to be more useful. There have been dozens of bug fixes across the application, as well as fixes to the build and testing infrastructures.

Bug fixes in this release focused on items reported by people using Chandler regularly; in particular, issues users found using the Chandler dashboard. The 0.7.4 release is the fourth in a series of ongoing releases since Chandler Preview 0.7.0 intended to respond to the ongoing feedback received from users. Additional releases improving Chandler Desktop are planned and ongoing.

Chandler Desktop 0.7.4 is available for download for Windows, Mac, and Linux at:

http://chandlerproject.org/download

Additional information is available from the Chandler Project homepage.

The bugs fixed in this release include:

• #6629 testing framework bug: KeyError:
• #7894 Events should be marked as DONE when end-date/times roll by, but not ‘Purged’ to DONE section
• #8658 Missing documentation on en_GB locale requirement
• #8814 After Preview is frozen, we should contact volunteer localizers to get them started
• #9928 Recorded Scripts: playback too sensitive to time zone settings
• #10128 MinCyg download on Chandler page missing some binaries
• #10498 Recorded script recTestAllDay passing even though it is creating a note
• #10625 Save when dragging event lozenges in the calendar
• #10662 error while deleting office cal
• #10750 TCEUT0007 - Sending an update to an invite doesn’t trigger sending the mail
• #10909 Chandler does not build on 64-bit Ubuntu Gutsy Gibbon
• #10916 PyDeadObjectError from wxTimedEventsCanvas
• #10937 Start-up screen that directs people to demo movies
• #10948 Entire recurring series keep popping into NOW but no evidence of global edit
• #10999 gdata plugin ends up as an .egg in plugins/ others are .egg-link
• #11110 Traceback when renaming a non-visible collection
• #11375 Use of delete key in quick entry field
• #11388 New items with a “/” anywhere in the title don’t get created
• #11396 recTestNewEvent fails on intel leopard tbox
• #11428 Kernel protection error double clicking in calendar
• #11444 Redesign export on quit
• #11454 Plugin install fails if no write access to CHANDLERHOME/plugins
• #11475 Nov 12th, 2007 Weekly PPD Meeting keeps popping back to NOW
• #11479 wxGrid fails to send EVT_GRID_EDITOR_HIDDEN
• #11494 It’s possible to have a collection be subscribed but not appear in the sidebar
• #11498 Need to handle cosmo response 409 to see if duplicate icaluids reported
• #11513 A couple exception raising statements are missing proper module name
• #11514 Localization scripts leveraging build_lib.runCommand fail on Windows
• #11531 Need a tool to compare Chandler.pot with submitted Chandler-LOCALE.po
• #11556 0.7.3 RC1 Chandler fails to launch with ValueError: An error occured while creating VM
• #11562 Events don’t auto triage to now when changing time of recurring event
• #11573 distIndex needs to be fixed to deal with the ~ in .deb files
• #11577 wx stock labels in English when starting on non-English system
• #11578 recorded script recTestNewEvent fails on Leopard
• #11597 Item I edited shows up as Unread in PPD collection
• #11602 Traceback borked my PPD collection
• #11604 Not able to create Chandler HUb Account - Generating Timeout error
• #11606 Failed to import record ItemRecord
• #11616 Traceback using context menu during script recording
• #11625 Using UI repo view from bg thread
• #11640 gettext needs to be built in external for mac and windows
• #11645 make install fails on leopard with error: egg creation failed
• #11660 Sending email to yourself in Chandler causes false-positive ‘Unread’ status and ‘popping into Now
• #11661 Only pop the NEXT OCCURRENCE into NOW if there has been a global edit.
• #11663 print statements in production code
• #11666 Recorded Script: mini cal nav does not work in Leopard on playback
• #11692 Subscribe to Google Calendar results in Subscribe Error
• #11697 Recorded Scripts don’t handle tabbing into notes DV field
• #11701 Add the German translation to the SVN trunk Makefile and releases
• #11702 Update debug plugin for repository as egg
• #11734 Update the French po for 0.7.4
• #8447 recorded scripts don’t work for dialogs
• #8772 Recorded script recTestKeepOutOfDashboard fails
• #9442 Recorded script quick entry creation of an item with apostrophe in title generates invalid python
• #9714 Script recording - triage button doesn’t get clicked on playback
• #9758 Script recording - unable to name an event on creation
• #9768 Script Recording - scripts fail to stamp items on playback
• #9780 Script recording - script too sensitive to event time on playback
• #10187 browse never catches AssertionErrors
• #10709 timezone display error
• #11121 Land the recorded_scripts branch
• #11150 Recorded scripts focusWindow.GetName() error when using quick entry
• #11172 Changing UI indication for working hours
• #11181 webbrowser.open is unreliable
• #11194 clicking on outgoing mail in the accounts dialog scrolls it on the top hiding the other 2 options
• #11390 gutsy and leopard tbox logs don’t include func test logs
• #11431 Inconsistent wording for protocol: type vs protocol
• #11433 Recorded scripts finds bug in wxGrid on Leopard
• #11462 Unstamping as mail after attempting to remove from Dashboard leads to AssertionError: index (n) out of range (n) and python crash on closing app
• #11507 Emails sent from Chandler don’t display First Name, Last Name in the From column
• #11528 Traceback when canceling a “collections and settings” export
• #11547 App crash on compact
• #11569 TestMulti fails intermittently on Linux
• #11574 Tip of the day
• #11582 Land the wx tarball for wxPython 2.8.7.1
• #11583 Recorded scripts UnboundLocalError: ‘window’ referenced before assignment
• #11627 Deleting imap account and adding another leads to exception
• #11708 Difficulties replacing TestEnableTimeZones with recorded script

Thanks for your interest in Chandler Desktop!

The Chandler Project is pleased to announce the 0.12.0 release of Chandler Server (Cosmo)!

Chandler Server is a server and Ajax web UI for managing and sharing calendars, events, and tasks. It implements open data standards including CalDAV, WebDAV, Atom, and Atompub.

This release supports a standalone WAR form of Cosmo ready to drop in to an existing Tomcat installation. A security issue allowing unauthorized access when a collection had been shared was fixed. A number of smaller bugs have also been fixed for Unicode usernames, error logging, and the calendar web UI.

Chandler Server 0.12.0 is available for download as a ready-to-run bundle at:

http://chandlerproject.org/serverdownload

and the source code is available from subversion at:

http://svn.osafoundation.org/server/cosmo/tags/rel_0.12.0

Send us feedback at the open mailing list (no subscription required):

chandler-users at osafoundation.org

We look forward to hearing from you!

The bugs fixed in this release include:

• #10816 Document how to deploy Cosmo into Tomcat
• #11101 unicode characters in username break admin ui
• #11442 overlaid event continues to be displayed in the color of the unselected calendar
• #11481 deleting account not working exactly as expected
• #11487 including records with dulicate icaluids succeeds
• #11554 Incorrect, possibly scary confirmation prompt when deleting subscriptions
• #11591 MC protocol needs its own security component
• #11754 retryfilter no longer works for dav
• #11755 server trying to update item in read-only service call
• #11757 invalid http method causes errors in log
• #11572 when allday is checked, time should be disabled
• #11721 February 29th not displayed in 2008

There was no change to the database schema for Chandler Server in version 0.12. Instructions for upgrading from previous versions of Chandler Server can be found at: <http://chandlerproject.org/Developers/ServerBundleInstallation#Upgrading%20from%20previous%20versions>

The Chandler Project is pleased to announce the 0.9.1 release of Chandler Server (Cosmo)!

Chandler Server is a server and Ajax web UI for managing and sharing calendars, events, and tasks. It implements open data standards including CalDAV, WebDAV, Atom, and Atompub.

New in this release is the ability to overlay multiple calendar collections and subscriptions onto a single calendar view, and the ability to create new collections via the web UI. Also improved in compatibility with iCal 3.0’s use of CalDAV, and support for more characters in usernames.

Chandler Server 0.9.1 is currently available for download as a ready-to-run bundle at:

http://chandlerproject.org/serverdownload

and the source code is available from subversion at:

http://svn.osafoundation.org/server/cosmo/tags/rel_0.9.1

Send us feedback (no subscription necessary) at the open mailing list:

chandler-users [at] osafoundation.org

We look forward to hearing from you!

This is a bugfix release for Chandler Server 0.9.0 and is recommended for general usage. Chandler Server 0.9.0 was not released because of a large slowdown caused by a corrupt build of an upstream library.

The bugs fixed in Chandler Server 0.9.0 and 0.9.1 are:

• #6194 Overlays
• #9715 Caching of Atom content not working properly in Firefox
• #10678 Cannot log in from IE 7 to production Chandler Hub 0.7.0-r5487
• #10734 Some characters in usernames cause trouble
• #10889 Log 5xx in /pim
• #10890 Log 5xx in /mc
• #10918 cosmo handles allday events incorrectly in some time-range query cases
• #11019 cosmo allows null displayName, which results in server error
• #11022 server bundle release notes point to the wrong place
• #11050 Spurious “Unsaved Changes” clicking off final item in recurrence
• #11068 Error deserializing XML attribute
• #11105 weird hibernate error seen on lab.osaf.us
• #11212 Collection overlay: list jumps around when it’s scrollable
• #11213 Using mini cal, quick jump, or next week navigation on canvas with overlay broken
• #11221 Incorrect subscription instructions for iCal 2.x with published collections
• #11241 Same-title events disappear from iCal 3 after being triaged
• #11249 empty title causes 500
• #11297 Collection creation and deletion bug
• #11372 Slowdown in Cosmo 0.9.0

A summary of known issues in this release is available:

http://chandlerproject.org/knownissues

This version of Chandler Server contains database schema changes from previous versions. Instructions for upgrading from previous versions of Chandler Server can be found at:

http://chandlerproject.org/Developers/ServerBundleInstallation#Upgrading%20from%20previous%20versions

Thanks for your interest in Chandler Server!

The Chandler Hub has been updated to Cosmo 0.7.5. Since the last announced Hub update, we’ve updated the service five times with new bugfix releases of Chandler Server (Cosmo).

The major improvements include:

• Full UI support for Safari browsers
• Multiple fixes to triage status handling between Chandler Desktop and Chandler Server
• Supports browsers set to widths greater than 1600 pixels
• URLs presented for webcal-based downloads now working
• Support for more punctuation characters in titles
• Editing recurring events works better in multiple situations
• Fix for the edited-by column in the dashboard view to show more useful data
• Multiple bugs fixed which were creating user-visible error messages
• Lots of individual feature and visual improvements and bug fixes

Please see the Cosmo blog channel for additional information about each individual release.  More neat features appear on the horizon from new Cosmo development.

As always, we welcome individuals and groups to try the free and open Chandler Hub service in addition to other Chandler Project components.