Veracity (software)

Last updated
Veracity
Developer(s) SourceGear LLC
Initial releaseOctober 18, 2010;9 years ago (2010-10-18)
Stable release
2.5 / March 5, 2013;6 years ago (2013-03-05)
Written in C
Operating system Cross-platform
Platform CLI
Type Revision control
License Apache License v2
Website veracity-scm.com

Veracity is an open source distributed version control system primarily written by SourceGear LLC which versions not only the artifacts placed under version control in the repository, but also associated data for features such as the integrated bug tracking system and agile build management tool. [1] [2] Written in C and JavaScript, Veracity is released under the Apache License and has a publicly available code repository, [3] however it is still mostly developed by SourceGear with limited community involvement. [4]

Contents

Integrated Bug tracking

Veracity's ability to tie a bug tracking system to specific versions of the repository artifacts in a distributed way allows a user to easily keep the bug tracking database in sync with the artifacts in every clone of the repository. [5] But, Veracity bug tracking data is only one data set which is versioned along with the repository artifacts in a "distributed database". Other such data includes a user list enabling built-in user access controls; and file locks (Veracity supports a "lock" mechanism similar to many traditional client-server version control systems). [2] How and where the decentralized database is stored is intended by the developers to be configurable. Veracity allows storing the repository separately from the working copy, and was designed to use an API which hides the back-end storage of the data, so that any given repository can use a wide variety of database formats or storage location. However, although a user can already have multiple working copies associated with a single repository, only one repository format (FS3) is actually supported as of version 1.0. [2] [3]

Usage

Some of Veracity's features are specifically intended to make the software more attractive in a corporate environment. Veracity's authors feel this distinguishes it from other DVCSs such as Mercurial or Git, [6] which often seem targeted toward open-source communities at the expense of corporate users. [7] However, Damon Poole writes for Dr. Dobb's that DVCS in general, not just Veracity, can offer users just as suitable a solution as the centralized version control systems more commonly used in the corporate world; teams should consider all their options to select the best system for their project's needs. [8]

See also

Related Research Articles

Wiki software collaborative software that runs a wiki

Wiki software is collaborative software that runs a wiki, which allows users to create and collaboratively edit "pages" or entries via a web browser. A wiki system is usually a web application that runs on one or more web servers. The content, including previous revisions, is usually stored in either a file system or a database. Wikis are a type of web content management system, and the most commonly supported off-the-shelf software that web hosting facilities offer.

The Concurrent Versions System (CVS), also known as the Concurrent Versioning System, is a free client-server revision control system in the field of software development. A version control system keeps track of all work and all changes in a set of files, and allows several developers to collaborate. Dick Grune developed CVS as a series of shell scripts in July 1986.

A component of software configuration management, version control, also known as revision control or source control, is the management of changes to documents, computer programs, large web sites, and other collections of information. Changes are usually identified by a number or letter code, termed the "revision number", "revision level", or simply "revision". For example, an initial set of files is "revision 1". When the first change is made, the resulting set is "revision 2", and so on. Each revision is associated with a timestamp and the person making the change. Revisions can be compared, restored, and with some types of files, merged.

Apache Subversion Free and open source software versioning and revision control system

Apache Subversion is a software versioning and revision control system distributed as open source under the Apache License. Software developers use Subversion to maintain current and historical versions of files such as source code, web pages, and documentation. Its goal is to be a mostly compatible successor to the widely used Concurrent Versions System (CVS).

Code Co-op peer-to-peer revision control system

Code Co-op is the peer-to-peer revision control system made by Reliable Software.

In software engineering, a project fork happens when developers take a copy of source code from one software package and start independent development on it, creating a distinct and separate piece of software. The term often implies not merely a development branch, but also a split in the developer community, a form of schism.

A bug tracking system or defect tracking system is a software application that keeps track of reported software bugs in software development projects. It may be regarded as a type of issue tracking system.

In software development, distributed version control is a form of version control in which the complete codebase, including its full history, is mirrored on every developer's computer. This enables automatic management branching and merging, speeds up of most operations, improves the ability to work offline, and does not rely on a single location for backups.

Mantis Bug Tracker free and open source, web-based bug tracking system

Mantis Bug Tracker is a free and open source, web-based bug tracking system. The most common use of MantisBT is to track software defects. However, MantisBT is often configured by users to serve as a more generic issue tracking system and project management tool.

Darcs distributed version control system

Darcs is a distributed version control system created by David Roundy. Key features include the ability to choose which changes to accept from other repositories, interaction with either other local (on-disk) repositories or remote repositories via SSH, HTTP, or email, and an unusually interactive interface. The developers also emphasize the use of advanced software tools for verifying correctness: the expressive type system of the functional programming language Haskell enforces some properties, and randomized testing via QuickCheck verifies many others. The name is a recursive acronym for Darcs Advanced Revision Control System.

Open-source software development is the process by which open-source software, or similar software whose source code is publicly available, is developed by an open-source software project. These are software products available with its source code under an open-source license to study, change, and improve its design. Examples of some popular open-source software products are Mozilla Firefox, Google Chromium, Android, LibreOffice and the VLC media player. Open-source software development has been a large part of the creation of the World Wide Web as we know it, with Tim Berners-Lee contributing his HTML code development as the original platform upon which the internet is now built.

The following is a comparison of version-control software. The following tables include general and technical information on notable version control and software configuration management (SCM) software. For SCM software not suitable for source code, see Comparison of open-source configuration-management software.

A software repository, or “repo” for short, is a storage location for software packages. Often a table of contents is stored, as well as metadata. Repositories group packages. Sometimes the grouping is for a programming language, such as CPAN for the Perl programming language, sometimes for an entire operating system, sometimes the license of the contents is the criteria.

ikiwiki wiki software that stores pages in a standard revision control system

ikiwiki is a free and open-source wiki application, designed by Joey Hess. It is licensed under the terms of the GNU General Public License, version 2 or later. ikiwiki is written in Perl, although external plugins can be implemented in any language.

Fossil (software) distributed version control system, bug tracking system and wiki server

Fossil is a distributed version control system, bug tracking system and wiki software server for use in software development created by D. Richard Hipp.

Plastic SCM is a cross-platform commercial distributed version control tool developed by Códice Software Inc. It is available for Microsoft Windows, Mac OS X, Linux, and other operating systems. It includes a command-line tool, native GUIs, diff and merge tool and integration with a number of IDEs. It is a full version control stack not based on Git.

In revision control systems, a repository is a data structure which stores metadata for a set of files or directory structure. Depending on whether the version control system in use is distributed or centralized, the whole set of information in the repository may be duplicated on every user's system or may be maintained on a single server. Some of the metadata that a repository contains includes, among other things:

An application strings manager is a software tool primarily designed to optimize the download and storage of strings files used and produced in software development. It centralizes the management of all the product strings generated and used by an organization to overcome the complexity arising from the diversity of strings types, and their position in the overall content workflow.

References

  1. Producing Open Source Software: How to Run a Successful Free Software Project by Karl Fogel
  2. 1 2 3 Version Control By Example by Eric Sink
  3. 1 2 Veracity, a New DVCS Based on a Distributed Database by Abel Avram on Jul 19, 2011
  4. O'Reilly OSCON 2011: Introduction to Veracity by Eric Sink
  5. Distributed Bug Tracking Avoids Out-of-Sync Bugs and Code by Paul Roub on July 1, 2011
  6. SourceGear News on July 21, 2010
  7. The State of DVCS by Michael Maddox on January 21, 2011
  8. Centralized vs. Distributed SCM by Damon Poole on September 13, 2011