AccuRev® ServerThe program that manages the AccuRev® repository and handles commands issued by AccuRev client programs. See also client program.The process of enabling a workflow in AccuRev so that the workflow can be used to automate issue processing and enforce compliance with your SCM policies. You activate a workflow by setting conditions that issues must meet in order to be subject to the workflow.In the version graph of an element, version A is an ancestor of version B if there is a direct line of descent (possibly including merges) from A to B. See predecessor (or direct ancestor). 'A is an ancestor of B' is equivalent to 'B is a descendant of A'.The 'path' (sequence of streams) through the depot's stream hierarchy, leading from a particular workspace or stream up to the depot's root stream. See also stream path.A date-timestamp setting for a stream, affecting which versions the stream inherits from its parent stream: for each element, the version inherited is the one that was in the parent stream at the basis time. See also snapshot.A particular ancestor of the version specified in a Patch, Revert, Diff, or Send to Issue command. The series of versions between the basis version and the specified version constitute the 'recent changes' to be patched into (or removed from) the target. Similarly, a change package entry consists of all the versions between a specified basis version and a specified head version.A set of entries, each in the form of a basis-version/head-version pair, recorded on the Changes tab of an issue record. The change package records the changes to one or more elements, made to implement the feature or bug fix described in that issue record. Each entry in the change package describes changes to one element: the changes between the basis version and the head version. See also patch.In a text-file merge (or patch) operation, a location where the two contributors being merged differ from each other. The Merge tool highlights and counts the change sections. It also tracks the conflicting changes (conflicts) -- the subset of change sections in which both contributors differ from the closest common ancestor. Conflicts must be resolved by human intervention. See also difference section.Stopping to save a version of an element, then proceeding to make additional changes to the element.(of two versions of an element) The most recent version that is an ancestor of two specified versions. Used in a merge operation to minimize the amount of work required to combine the contents of the two specified versions. See also merge, version graph.(parallel development) The practice of having two or more users concurrently work on the same project -- modifying the same version-controlled elements. See also serial development.A change to the contents of a file element, recorded in a new version created with the Keep command. For a symbolic-link element, a change to the target pathname is a content change. For an element-link element, a change to the target element is not considered a content change to the link. See also namespace change.The version of an element that currently appears in a particular workspace or stream. (It's also possible that a given workspace/stream might not contain any version of a given element.) The current version can be directly active in the workspace/stream; if not, it is inherited from the parent stream. See also passive.The term used to refer to element versions that are not associated with any issue. Also referred to as unaffiliated changes. See Unaffiliated Changes ("Dark Matter") on page 107.The portion of the AccuRev repository that stores the entire history of a particular directory tree. See also element, version.In a text-file-comparison operation, a location where the two files (or two versions of the same file) differ from each other. The Diff tool highlights and counts the difference sections. See also change section.The portion of a depot in which AccuRev maintains a permanent copy ('storage file') of each newly created file version. See also metadata.A file system object that can contain files and other folders. Each version of a folder records a change to its name and/or pathname location in the depot's folder hierarchy. See also directory.A stream that uses user-defined rules to control whether changes promoted into it can be promoted out of it. Gated streams cannot be created using the Web UI, but they are displayed in the StreamBrowser. See also staging stream.Any stream that has been Removed and which by default no longer appears in the StreamBrowser™. Hidden streams can be viewed in a grayed-out state by checking the Include hidden streams checkbox.The instance of the AccuRev Server process that handles all transactions that change the status of elements in the master repository. Only the master server can write data to the repository. See replica server.An element has '(member)' status in a workspace or stream if one of its versions is in the default group of that workspace or stream. An element with '(member)' status is said to be active in that workspace or stream; otherwise, it's passive.Version X, in a workspace or stream, has '(overlap)' status if the parent stream's current version of the element contains changes that are not reflected in version X. (That is, the parent stream's version is not an ancestor of version X.) Such a version cannot be promoted to the parent stream; the user must create a new version with a merge operation, combining version X with the parent stream's version. The new, merged version can then be promoted. Similarly, an overlap can exist between the versions in two dynamic streams. See also deep overlap.(concurrent development) The practice of having two or more users concurrently work on the same project -- modifying the same version-controlled elements. See also serial development.A set of versions of a text-file element -- typically, containing the 'recent changes' made in one workspace. Also, the merge-like operation that incorporates those changes into another version of the same element. See also merge, basis version, head version, change package, reverse patch.(direct ancestor) The real version from which a given version was derived. A version and its predecessor are not necessarily located in the same workspace stream. In the Version Browser, a version and its predecessor are connected by a black line. (Exception: a version created by the Revert command is connected to its predecessor by a dashed blue line.) In the version graph of an element, version A is an ancestor of version B if there is a direct line of descent (possibly including merges) from A to B.(AccuWork) A query that appears in the Query List pane only for the user who created it. See also public query.The operation (Promote command) that transitions a version from being active in one workspace or stream to being active in the parent stream (or some other stream). This operation creates a new virtual version in the parent stream; the virtual version provides an alias for the real version, which was originally created in some user's workspace. See also version.The operation (CLI: purge command; GUI: Revert to Backed command) that discards the changes made to an element in a given workspace or stream.A version of an element, created in some user's workspace, recording a change to the contents and/or pathname of the element. See also version, virtual version.The portion of the repository that stores data other than the contents of element versions. See also file storage area.An operation that removes a selected set of changes from the current version of a text-file element. See also patch, change package.The time at which a workspace's most recent search for modified files was initiated. Such searches are performed by the Update command and by certain File Browser searches. See also update level.The practice of ensuring that multiple users do not work concurrently on the same version-controlled file. See also parallel development.In a workflow, an object that represents a phase in a development or release process. For example, your development process might have New, Scheduled, WIP (work-in-progress), and Closed phases, among others.A child of a gated stream that AccuRev creates automatically when you create or reparent a workspace off the gated stream. Staging streams are used to hold changes promoted to the gated stream until the successful completion of any job defined by the trigger associated with the gated stream (like a build or test, for example). You cannot create staging streams explicitly. See also gated stream.An element has '(stale)' status in a workspace if it is not currently active in the workspace, but a new version of the element has entered the parent stream. An update operation will overwrite the stale version with the parent stream's new version.An AccuRev snapshot. The term 'static stream' emphasizes the fact that snapshots are part of a depot's stream hierarchy. See also snapshot.A keyword (usually enclosed in parentheses) that reports the AccuRev-level status of a particular element in a particular workspace or stream. Commonly, multiple status indicators apply to an element. See also status.An element has '(stranded)' status in a workspace or stream if it's currently active, but there is no pathname to the element. This occurs when the element's directory (or a higher-level directory) is removed from the workspace or stream by the Defunct command or an exclude rule.The AccuRev data structure that implements a configuration of the elements in a particular depot. The configuration of a dynamic stream changes over time; the configuration of a snapshot (static stream) never changes. Each workspace has its own private workspace stream. See also workspace, stream hierarchy.A stream that has a 'basis time', affecting which versions it inherits from its parent stream. See also basis time, parent stream.The number of the most recently completed transaction for a particular depot. See also update level.In a workflow, an object that links one stage in a workflow with another; it represents how an issue may move from one workflow stage to another.The term used to refer to element versions that are not associated with any issue. Also referred to as dark matter. See Unaffiliated Changes ("Dark Matter") on page 107.The operation (Update command) that copies new versions of elements into a workspace from its parent stream.The most recent (highest-numbered) transaction whose changes have been incorporated into a workspace, through an update operation. See also scan threshold, transaction level.A person who uses an AccuRev client program to access (read and/or change) the data in the AccuRev repository. Access is granted only to those who login with a 'username' that was previously registered in the AccuRev repository. See also login.The directed-graph data structure that shows the ancestry of an element. The nodes are all the versions of an element, and whose lines indicate how later versions were derived from earlier versions. The Version Browser displays the version graph of an element.In a dynamic stream, a version of an element, created by the Promote command, which serves as an alias for (reference to) a previously created real version. In a workspace stream, a version created by the Send to Workspace or Anchor command, referring to the real version that the command 'checked out'.
| Borland |