Veracity (software)

Veracity
Developer(s) SourceGear LLC
Initial release October 18, 2010 (2010-10-18)
Stable release
2.5 / March 5, 2013 (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]

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

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
This article is issued from Wikipedia - version of the 9/8/2015. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.