Cosmo 0.6.1 Migration Meeting April 13th, 2007

Attendees: Jared, Ted, Mikeal, Adam, Randy, Priscilla, Aparna

Agenda

• Review what migration 0.6.1 is about
• Review high level plan to test migration
• IRC QA Sessions
• Next steps and action items

Notes

• We believe for a little while we will need to support both the old sharing format and the new one that uses morse code/eimml from Chandler Desktop till all existing users have been switched over. THe idea is to start encouraging people to switch over to new cosmo once it has been qualified by QA. We need to discuss this at the Preview Meeting on Monday on how do we stage moving people over to the new cosmo and by what time frame.

• Jared would like to have a zero-day breakage for 0.6.0.1 to 0.6.1 migration. So the idea is to make it as seamless for the users as possible. They will not have to export their data and reimport it like the last 0.5 to 0.6 migration.

• We discussed about targeting the next few collaborative QA sessions around testing data migration. Currently in the PreviewCountdown^? plan, cosmo 0.6.1 upgrade is scheduled for May 4th which would give us only 2 wednesdays and we have other cosmo 0.6.1 testing to take care of. We plan to do more than just 1 QA session a week for the next few weeks. We will start out with 2 next week on Wednesday and possibly Friday or Thursday. While we use one session for migration testing we could use the other for doing sharing tests from Chandler desktop against cosmo 0.6.1.

• For users still using cosmo 0.6.0.1, we will only support /dav URLs going forward. We will be very clear about this by publishing it on the chandler-users list, as well as FAQ, Help pages, release notes etc ( Now when I am writing up the notes, I am a little confused about this given in the new sharing world we support /cosmo and not /dav. I will send this to the list for clarification)

• Jared brought up a point about staging the migration as 2 steps process: first host name change from osaf.us -> hub.chandlerproject.org and then upgrade to 0.6.1. That way we can isolate users being affected by one change or the other.

• For testing data migration, Mikeal has requested Jared to give him a clean instance of cosmo 0.6.0.1 which will be populated with people's data during the QA session and then migrated to 0.6.1 and validated.

• Second part of the testing will involve getting a clone of production data on say lab.osaf.us. Having people generate more test data on it, run data migration and then validate the results.

• We want to include testcases revolving around modifications to recurrences particularly in this migration testing because of the specific changes made to it in this version. It could use some extra testing drill. Also the QA team will go thru existing Chandler Desktop testcase scenarios and add some specific ones to the migration test plan esp around recurrences, timezones, non-event items, etc

• Mikeal will run his automated tests on the pre-migrated and post-migrated instances as last time.

Action Items

• Jared will provide Randy a clone of production instance to run (unit-test) his migration script on. This will help us find bugs with the migration script upfront(rather than waiting right till the QA session)
• Jared will also create a vanilla instance of cosmo 0.6.0.1 by Monday for migration testing and let Mikeal know. For the QA session we will upload data on it, run the migration script and validate the data.
• Jared will also need to give us(QA) a clone of production instance to test the existing data once it is migrated. We will let Jared know when we need this (possibly after 1 and 2 above)
• Aparna to write up the Migration test plan and send it to the team for review by Monday.
• Aparna to send Sheila an agenda item for Monday's Preview meeting to discuss about the time frame for moving the existing users to the new cosmo server.

-- AparnaKadakia - 13 Apr 2007