Sun WorkShop TeamWare User's Guide

Glossary

Access control

A feature in Configuring you can use to control access to workspaces.

Branch (SCCS)

A delta or series of deltas that are placed off of the main line of deltas in an SCCS history file.

Bringover Create

The transaction used to copy groups of files from a parent workspace to a nonexistent child workspace. The new child workspace is created as a result of the transaction. All Configuring transactions are performed from the perspective of the child workspace; hence, the Bringover Create transaction "brings over" files to the child from the parent workspace. See also Bringover Update, Workspace, and Putback.

Bringover Update

The transaction used to update an existing child workspace with respect to files contained in its parent workspace. All Configuring transactions are performed from the perspective of the child workspace; hence, the Bringover Update transaction "brings over" files to the child from the parent workspace. See also Bringover Create, Workspace, and Putback.

Child workspace

A workspace that has a parent workspace listed in its Codemgr_wsdata/parents file. Development work is typically done in child workspaces and put back to parent workspaces after it has been tested. Configuring transactions are viewed from the child workspace perspective and all conflicts are resolved in the child workspace.

Codemgr_wsdata
directory

Every TeamWare workspace contains a "metadata" directory in its root directory named Codemgr_wsdata. Configuring stores data about the workspace in Codemgr_wsdata. The presence of this directory is the sole factor that defines it as a TeamWare workspace (as opposed to a normal directory). Configuring commands use the presence or absence of this directory to determine whether a directory is a workspace. See Workspace Metadata Directory for more information.

Configuring

The tool you use to manage Sun WorkShop TeamWare workspaces. See Chapter 2.

Conflict

The condition that exists when a file has changed in both the child and parent workspace. Conflicts are identified by the Bringover Update transaction and are resolved by using the Resolve transaction.

Copy-Modify-Merge

The concurrent development model upon which Configuring is based. Using this model, multiple developers concurrently copy sources from a common area, modify the source in isolation, and then merge those changes with changes made by other developers.

Create

Used in Configuring transaction output. Files are said to be created if they exist in the source workspace and not in the destination workspace, and are copied into the destination workspace as part of a Bringover or Putback transaction.

Default path

The branch in an SCCS history file upon which the next delta will be added. This is indicated in a history file by a solid line.

def.dir.flp

The default FLP shipped with Configuring is def.dir.flp; this FLP recursively descends directory hierarchies and lists all files for which SCCS history files exist. See FLP.

Delta

The set of differences between two versions of a file checked into SCCS. When you check in a file, SCCS records only the line-by-line differences between the text you check in and the previous version of the file. This set of differences is known as a delta. The file version that you initially checked out was constructed from a set of accumulated deltas. The terms delta and version are often used synonymously; however, their meanings are not the same. It is possible to retrieve a version that omits selected deltas. See Version.

FLP

An FLP or File List Program is a program or script that generates a list of files that Configuring uses during Bringover and Putback transactions. See def.dir.flp.

Freezepointing

The Sun WorkShop TeamWare tool you use to make snapshots of workspaces (or portions of them) at important junctures or "freezepoints." See Chapter 8.

g-file (SCCS)

The working copy of a file retrieved from an SCCS history file by the
sccs-get command.

History files

When you initially put a file under SCCS control, a history file is created for the new SCCS file. The initial version of the history file uses the complete text of the source file. The initial history file is the file that further deltas are compared to. Owing to its prefix (s.), the history file is often referred to as the s.file (s-dot-file).

Integration Request Identifier

A "password" required by Putback Validation before Configuring will allow a putback.

Integration workspace

A workspace to which multiple developers put back their work.

Lock

To assure consistency, the Configuring file transfer transactions Bringover and Putback lock workspaces while they are working in them. Locks are recorded in the Codemgr_wsdata/lock file in each workspace; the Configuring commands consult that file before acting in a workspace.

Merge

To produce a single version of a file from two conflicting files. Accomplished with the assistance of the Merging tool.

Merging

The Sun WorkShop TeamWare tool you use to merge two different versions of the same file. See Chapter 6.

MR

Modification Request. A "password" required by Versioning before a file can be checked in.

Notification

A Configuring feature that mails notices of events, such as changes to files or directories, to users.

Parent workspace

A workspace that has a child workspace. Parent workspaces are typically used as integration areas, because development, testing, and conflict resolution occur in child workspaces.

Putback

The transaction used to update a parent workspace with respect to files contained in its child workspace. All Configuring transfer transactions are performed from the perspective of the child workspace; the Putback transaction "puts back" files to the parent from the child workspace. See also Bringover Create, Bringover Update, and Workspace.

Putback Validation

A Configuring feature that allows you to control which putbacks are allowed to a specific workspace.

Reparent

To change the parent of a child workspace.

Resolve

To produce a new delta of a file from two conflicting deltas. See Merge and Conflict.

Root directory

The top-level directory of a Configuring workspace. This directory's path name is the name by which the workspace is referred.

RTI

Request To Integrate, the heading used to record an Integration Request Identifier in a workspace history file.

SCCS Delta ID (SID)

A SID is the number used to represent a specific delta. This is a two-part number, with the parts separated by a dot (.). The SID of the initial delta is 1.1 by default. The first part of the SID is referred to as the release number and the second, the level number. When you check in a delta, the level number is increased automatically.

SCCS file properties

Properties that you can assign to individual files.

SCCS history file

The file that contains a given file's delta history; also referred to as an "s-dot-file." All SCCS history files must be located in a directory named SCCS, which is located in the same directory as the g-file. See g-file.

SCCS Mergeable ID (SMID)

A SMID is a number generated using the Xerox Secure Hash Function that ensures that every delta is uniquely identifiable, even if its SID is changed.

SID

See SCCS delta ID.

SMID

See SCCS Mergeable ID.

Uncheckout

To return a file to the state it was in before the most recent check out.

Undo

To return a workspace to the state it was in before the most recent Bringover or Putback transaction, thereby "undoing" the action of the transaction.

Update

Files are said to be updated during a Bringover or Putback transaction if they exist in both the source workspace and in the destination workspace, and have changed in the source workspace. The SCCS history file in the destination workspace is updated with new deltas from the source workspace.

Version

When you check in a file, SCCS records only the line-by-line differences between the text you check in and the previous version of the file. This set of differences is known as a delta. The file version that you initially checked out was constructed from a set of accumulated deltas. The terms delta and version are often used synonymously; however, their meanings are not the same. It is possible to retrieve a version that omits selected deltas. See Delta.

Versioning

The Sun WorkShop TeamWare tool you use to manage Sun WorkShop TeamWare files. See Chapter 5.

Workspace

A workspace is a specially designated directory, its subdirectories, and the files contained in those directories. Usually each developer on a project works in their own isolated workspace concurrently with other developers programming in other workspaces. Configuring provides utilities to manage workspaces. See Chapter 2.

Workspace hierarchy

A hierarchy of parent and child workspaces in which programmers and release engineers can develop, test, share, and release software products.