Common VCS terms often interpreted differently, which may cause some confusion. Listed here are the terms that you’ll encounter in Upsource with the definitions adopted by Upsource.

Term Definition
Branch An off-spring of the code base. Once created, it can evolve independently as a side-line without affecting the development process in a trunk (master) and other branches.
Head The most recent revision of a code base in a given branch or a trunk (master).
Commit A single action of submitting changes made in a local working copy back to a repository. A commit can also refer to a revision that is created as a result of committing. These two terms are interchangeable within the scope of Upsource.
Committer A VCS user who has made changes to the code base in the repository. A committer may or may not be a registered Upsource user.
Revision Generally, a revision is the state of the code base in the repository at a particular point in time. It also refers to the changes made to one or several files (changeset) that are committed to the repository in a single action. The terms revision and commit are used interchangeably within the scope of Upsource.
Project A result of processing a VCS repository, several repositories or a part of a repository by Upsource whereby it creates an index of revision history and source code in each revision. Within a project, a number of services is provided to end users such as viewing and mining the revision history, comparing revisions, browsing and searching the code base.
Review A task that is associated with one or more revisions or branches. In its live span the review goes through different stages. It is created as a request to examine the revision(s), marked completed when the examining is done and changes approved, then closed when no further action is required or expected. A review may also contain a discussion thread in form of comments and replies.
Trunk Also: Master, Baseline. A main line of the development process. In a VCS tree, a trunk can have off-springs called branches that can be developed independently and then merged back to a trunk.