Checking in a non-tip revision

There are a couple of scenarios where you may need to check in a non-tip revision. Most obvious is if you have checked out a non-tip revision, but it may also occur if parallel development is enabled. In this case, several users may have checked out the same file and others have checked in their changes before you get a chance.

Since Team Coherence remembers where files were checked out to and which revisions of these files were checked out, it is not necessary to specify a revision when checking in files. Any non-tip revisions that are checked in will result in a branch revision being created if the file has changed.

To check-in files, including non-tip revisions, select the relevant objects in Version Manager and select Action/Checkin:

Enter a comment for the new revisions and press the OK button. Once the objects have been checked in, the status dialog box will be displayed:

Any files where a non-tip revision was checked in, and a new revision was branched, will be highlighted in the status dialog.

A Branch revision is a revision where a new line of development has begun and is indicated in Version Manager by a new level of revision caption (for example, the first branch of revision 1.1 will be 1.1.1.0):