[Cosmo-dev] Re: changing the format of modification recurrence-ids in eim

[Ted Leung]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

If we need to do it then let's do it before 0.6.1.  Otherwise the  
migration and other logistics will eat us later.

Ted

On May 9, 2007, at 9:37 AM, Mikeal Rogers wrote:

>
> On May 9, 2007, at 9:17 AM, Morgen Sagen wrote:
>
>>
>> On May 8, 2007, at 5:49 PM, Brian Moseley wrote:
>>
>>> On 5/8/07, Grant Baillie <grant at osafoundation.org> wrote:
>>>
>>>> FWIW, I think Chandler clients would have to understand (at least
>>>> temporarily) both old and new formats, or dump and reload will be
>>>> broken and that will make me cry.
>>>
>>> really?
>>
>>> are you trying
>>> to maintain complete compatibility across checkpoints?
>>
>> Sure, as much as possible we try to keep people's existing dump  
>> files usable by newer versions of Chandler.  I think in this case  
>> it should be easy for Chandler to support both formats since  
>> parsing/generating them is limited to two methods.  What will  
>> *not* work, however, would be if Cosmo started using the new  
>> format for a previously published collection.  So I think we would  
>> require that the server-side collections be wiped out and that  
>> Chandler republish them.
>
> With this being the case I'd like to see the change go in before  
> the next rc.
>
> We haven't shipped yet, we have a small window, if it's going to  
> reduce the complexity for developing/testing eim based sharing we  
> should make this change now.
>
> -Mikeal
> _______________________________________________
> cosmo-dev mailing list
> cosmo-dev at lists.osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/cosmo-dev

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFGQgKbYCjW/J06/U8RAj6wAJ4ocRx4sNNZWJI4TXFqdTFX2LnFAwCfXAI4
dsOq0GuD5dGPE7Eux/ogp6A=
=Y/9y
-----END PGP SIGNATURE-----