[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Proposed workflow for upgrade wizard for 1.2 to 1.3
- Subject: Re: Proposed workflow for upgrade wizard for 1.2 to 1.3
- From: David <..hidden..>
- Date: Wed, 20 Jul 2011 10:35:52 +1000
On 20/07/11 02:41, Chris Travers wrote:
I am hoping to start work on an upgrade wizard for 1.2 to 1.3 next
week, so I figured it would be a good idea to discuss my thoughts here
The upgrade wizard would guide you through the process of migrating
data from 1.2 to 1.3. It would utilize parts of the 1.3 codebase but
operate against a 1.2 codebase as a database superuser.
Screen 1: Login (login name, password, database to upgrade)
Screen 2: We will now check out your database for problems that might
interfere with the upgade. (run queries to check against new unique
constraints that are known to be problematic. If problem found go to
three, if no problem found go to 4)
Screen 3: Problem found.... List problem records. Give an
opportunity to correct the problem in non-destructive way. Then
continue running query checks, For each problem found repeat this
screen. When no more problems found, go to screen 4. Note this will
not correct some problems (missing or unrecognized countries) which
will be addressed post-migration.
Screen 4: Success! You are now ready to upgrade! Prompt for path to
contrib files, default country, and default links for AR and AP. Run
the main migration script. Look for unrecognized cities, states, and
countries. If found, go to screen 5, if not go to screen six.
Screen 5: List addresses with problems, and the customer/vendor
accounts they are connected to. Provide an opportunity to
Screen 6: Create database users and passwords for existing LSMB
users. Copy list to screen. Passwords will be valid for one week
after creation and users will be prompted to change them on first
Will this create a new database? ie, non-destructive to the 1.2.x DB? Or
will it use a copy created for the purpose of migration?
Are the opportunities to make corrections going to be scripted or do we
dive into the database by hand?
Otherwise, I'm looking forward to it.