[Chandler-dev] Items in multiple collections -- avoid for now (until Cosmo 0.7)

[Morgen Sagen]

Recently I discovered (and Randy quickly fixed) a Cosmo bug where a
change to a recurring event in  one collection wasn't being reflected
in other collections the item was also in on the server.  However,
this fix won't be on the Hub until 0.7 is installed there, so it is
probably a good idea for Hub users to not copy recurring events from
one shared collection to another.  I suppose we could change Chandler
code to prevent such copying, but I don't know if it's worth it at
this point, since the Hub upgrade should happen in a few weeks.

So for now, don't drag recurring events between shared collections.

Thanks,
~morgen

P.S.  If you haven't already, please upgrade your Chandler to the
latest checkpoint (or SVN) so we can see if the mysterious UUID-titled
events are due to old clients or a current bug.

   http://downloads.osafoundation.org/