[Cosmo-dev] Data migration testing for 0.6.1
aparna at osafoundation.org
Tue Apr 10 16:06:55 PDT 2007
You bring up a good point Morgen. There are more subtleties to test
in this migration than the previous.
Jared, Mikeal, Adam, Morgen, Ted: can we have a meeting tomorrow or
Thursday(after the cosmo meeting at 3 pm) to go over all the cases we
would like to cover during migration?
We can develop the migration test plan based on 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
More information about the cosmo-dev