Previous Table of Contents Index Next
Perforce 2012.3: P4Sandbox User's Guide

Appendix B
This glossary describes P4Sandbox-specific terms. For Perforce-specific and general version management terms used in Perforce documentation, see the Perforce User's Guide, "Appendix A: Glossary."
See the P4 User's Guide's Glossary for the following terms:
A company's or team's main Perforce server or depot; the server that you connect to a P4Sandbox to which you merge down and copy up changes (see merge down and copy up paradigm). Also called a central server.
P4Sandbox's functionality that enables you to check changes in and out without requiring an active connection to a shared service. You connect to a shared service through the remote depot when merging down and copying up changes.
Stream for long-term projects and new features. A development stream is less stable than its parent stream.
Any P4Sandbox stream that is not a mirror stream. This includes mainline streams that are not associated with a shared service, as well as any development streams.
The paradigm and process for managing change through a hierarchy of codelines. Codelines, represented within Perforce as streams, exist in a hierarchy of stability, from more stable to less stable. You merge down changes from more stable streams to less stable streams, and copy up changes from less stable streams to more stable streams. In P4Sandbox, you must merge down changes from the mirror stream before you copy up changes from any local stream.
A mirror stream is any mainline stream associated with a shared service through a branch mapping.
Type: mainline
Owner: p4sandbox
The branch form name generally matches the stream name convention: "$depot_$streamshortname"
For example, the stream "//streams/foo" has a cor­responding branch form named "streams_foo".
The P4Sandbox server; also means the local implementation of P4Sandbox.
The broker that implements P4Sandbox functionality. All user interactions are managed through this broker.
p4sandbox command
The p4d distribution used by P4Sandbox for the local server.
A GUI configuration tool (P4Sandbox Configuration Wizard) for creating and editing a P4Sandbox implementation. Creating a P4Sandbox also creates a hidden directory and updates a reference file. The location of the these files and directories is dependent upon your platform.
Directory containing the p4d databases and archive files.
P4USER=machine's default user
The collection of files installed by the P4Sandbox installer; specifically, the p4, p4sandbox, and p4sandbox-p4d executable files. It does not contain the db.* and versioned files included in a P4Sandbox server.
The .p4sandbox folder, all the db.* and versioned files it contains, and the process that listens on the configured P4PORT.
See also P4Sandbox.
The ability to create streams (called local streams) within P4Sandbox for specific tasks, such as bug fixes for a particular release, and determine codeline management and policies on these streams.
The mechanism by which P4Sandbox connects to the shared service. If you are using P4Sandbox with p4 use the p4 remote and p4 remotes commands. If using P4Sandbox with a graphical client application or plug-in, the P4Sandbox Configuration Wizard automatically establishes this connection during the setup process.
Shelving is the process of temporarily storing files on a Perforce server without checking in a changelist.
Automatic: Shelving that P4Sandbox performs in the background when you switch among task streams and workspaces and have unsubmitted changes.
Shelving that you perform when you switch among task streams and workspaces and have unsubmitted changes.
You can perform user-directed shelving from either p4 by issuing the p4 shelve command or from P4V by using the shelving commands available from the context menus.
A stream is a Perforce database object that describes information about a branch; in short, a "branch with brains."
There are four stream types: development, mainline, release, and virtual.
A local stream intended for a single specific task, and then abandoned once the task is complete; for example, a bug fix.
Task streams are a concept, not a specific stream type. There is no mechanical difference between a local stream and a task stream; the difference is solely in usage and not in how P4Sandbox handles the stream.
To switch from one task to another by switching from one stream to another. If you are using the P4V Stream Graph, you can switch tasks by moving the workspace icon between streams.
When you switch between streams, P4Sandbox automatically performs the following tasks:
The formatted files that store a file's history of content changes. For more information about versioned files, see the Perforce System Administrator's Guide, "Supporting Perforce: Backup and Recovery."
Stream for submitting changes directly to a parent stream.
See also the P4 User's Guide's Glossary for the following terms:
Also known as client form. Term means the entire form, both form name and contents.

Previous Table of Contents Index Next

Perforce 2012.3: P4Sandbox User's Guide
Copyright 2012-2013 Perforce Software.