•Backup your current development library.

• Save to files any text from open workspaces or from the Transcript window of your current development image.

•Merge your current development library and the new development library. You can either merge applications from your existing library into the new library or merge the new library into your existing library. No matter which direction you perform the merge, the merge operation only copies versioned maps and applications.

If you merge your existing library into the new library, you will leave all open editions and scratch editions of applications and maps behind -- if you do this, you should archive your existing library in case you need to refer to the information that wasn't copied into the new library.

If you wish to retain all open editions of maps and applications, you can merge the entire new library into your current library. This has the advantage of keeping all your work in one place, but it keeps all code, even code you may wish to discard. If the library becomes too large, you can clone it after you are satisfied with the migration and discard all open editions at that time.

•For each product version there are specific migration concerns. Each product version is covered in a separate chapter. You should start reading at the chapter describing the product version you are migrating from, and continue reading to the end of this book to understand the complete migration picture. You can perform the migration activities as you go.

•If you have changed any of the product applications, you should evaluate your changes and re-merge and test your changes in the new version of VA Smalltalk.

•Run any regression tests you have for your application against the new configuration.

•Once you are satisfied that the application performs as specified in the development image, you should package your application and execute your runtime tests.