Basic Concepts of TeamWare File Management

Bringover

• What is a bringover?

The transaction in which you copy one or more directories from the parent workspace to your own child workspace.

• Why do a bringover?

To furnish your workspace a copy of each directory and file you need to work on. Also, to refresh your workspace with the latest version of those directories and files.

• When should I do a bringover?

Often! TeamWare prompts you to do a bringover if your workspace contains old file versions. However, you should do another bringover each time you begin working on a set of files.

• How do I do a bringover?

For the first time: Configuring -> Actions -> Bringover Create

To refresh: Configuring -> Actions -> Bringover Update

Putback

• What is a putback?

The transaction in which you copy files you've changed from your own child workspace back to the parent workspace.

• Why do a putback?

To update the parent workspace with the changes you've made. Also, to let your teammates refresh their own child workspaces with your changes, so you're all working on the same version of the files.

• When should I do a putback?

Each time you finish making changes and want to notify other team members that the parent workspace has been updated.

• How do I do a putback?

Actions -> Putback

Freezepoint

• What is a freezepoint?

A snapshot of a directory that you have set aside at a particular point in time. You've "frozen" that version so that you can keep on developing the source code, and can come back to that version when you need to. A freezepoint is a lightweight but intelligent pointer to a specific file version.

• Why create a freezepoint?

To archive source code at a particular point in its life cycle. For example, to set a particular build aside for later reference, while you continue working on the next build.

• When should I create a freezepoint?

Freezepoints aren't obligatory, but you can create one whenever your project has a need to safeguard an old version of the code.

• How do I work with freezepoints?

To create a freezepoint: TeamWare -> Freezepointing -> Creation

To extract the whole file from a freezepoint: TeamWare -> Freezepointing -> Extraction

File Merge

• What is a merge?

The transaction in which you compare two versions of a file--the version from your child workspace and the version now in the parent workspace--side by side. There, youselectively merge the differences so that the two versions become one file that reflects changes from two developers. When you're doing a file merge, you can choose whether to ignore or incorporate each difference in the source code.

• Why do merge files?

To keep source code from "forking" as two developers change the same file. Also, to update the parent workspace with a single, current copy of that file.

• When do I do a file merge?

If you try to put back a file that someone else has already put back with different changes, TeamWare automatically brings up the Merging window with the two versions displayed. If you know in advance that two files need merging, you can bring up the Merging window yourself.

• How do I do a file merge?

TeamWare -> Merging