[Cosmo-dev] Data migration testing for 0.6.1
mikeal at osafoundation.org
Tue Apr 10 16:18:54 PDT 2007
The expectation here is that most people will be using old, already
released, Chandler clients through the next migration and that they
will still be using the old sharing methods.
Moving people between sharing accounts in Chandler hasn't been
discussed, and won't be fully addressed for the 0.6.1 release because
most of the dogfooders won't be using EIMML capable Chandlers against
osaf.us, and cosmo isn't responsible for migrating that data anyway.
We will need to have a plan for instructing our bleeding edge users,
I'm lookin' at you Andre : ), on how to migrate their shares to the
new sharing format, and for the Preview release of Chandler we'll
need a plan for instructing everyone on how to do the same.
EIMML testing is perhaps the largest part of them cosmo 0.6.1 release
testing, but migration with EIMML is not part of that.
On Apr 10, 2007, at 3:56 PM, Morgen Sagen wrote:
> With the transition from the old dual-fork ICS+XML shares to the
> new EIMML-based shares, it's going to have to be Chandler clients
> that migrate the data. Cosmo doesn't understand the old XML format
> that Chandler's been using to store all non-event-related data. I
> guess there are really two aspects to this migration: one which
> copies the old ICS+XML files into an 0.6.1 Cosmo instance, and then
> one where the person responsible for a given collection uses their
> Chandler to convert ICS+XML to EIMML (and then unpublishes the
> original dual-fork collection).
> On Apr 10, 2007, at 3:42 PM, Mikeal Rogers wrote:
>>> Yes, we are definitely planning a few IRC test sessions around
>>> 0.6.1 and we should cover migration testing during that.
>> For the first session next week I have this suggestion.
>> Rather than migrating all the osaf.us data we have jared host a
>> clean cosmo 0.6.0 and for the first 20 minutes of the session we
>> load it up with our accounts and data from Chandler and other
>> Then we have jared bring down the server, run his migration script
>> and update to 0.6.1.
>> Then we use the rest of the time in the session to find any issues
>> that may have happened during the migration.
>> With this process we find all the bugs that pertain specifically
>> to the same dataset migrated with the same subscription URLs
>> rather than testing all our data that's been migrated to different
>> URLs on the migrated instance. This would have flushed out a lot
>> of the issues we didn't catch last time in the migration testing
>> process until we went to production.
>> cosmo-dev mailing list
>> cosmo-dev at lists.osafoundation.org
> cosmo-dev mailing list
> cosmo-dev at lists.osafoundation.org
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 186 bytes
Desc: This is a digitally signed message part
Url : http://lists.osafoundation.org/pipermail/cosmo-dev/attachments/20070410/9f2bce03/PGP.pgp
More information about the cosmo-dev