SVKEdit

SVK is a pseudo-distributed version control system with powerful branching and merging capabilities and built upon proven Subversion technologies.

SVK is only "psuedo-distributed" rather than "distributed" because it is basically designed to work as a wrapper around an existing centralized workflow. Each developer can create a local mirror of a remote central repository and work on it locally, but these local mirrors are not fully-fledged repositories in their own right (ie. they cannot be published and shared with other developers, except indirectly by pushing changes back to the centralized server). By way of contrast, Git is an example of a truly distributed version control system in which all repositories are full-fledged, publishable peers.

See also

• Official product page: http://bestpractical.com/svk/
• Official wiki: http://svk.bestpractical.com/
• "Painless Merging with SVK: An Interview with Chia-liang Kao": http://www.oreillynet.com/pub/a/network/2005/09/20/painless-merging-with-svk.html
• Bieber Labs SVK tutorials: http://www.bieberlabs.com/wordpress/svk-tutorials/
  • Part 1: http://www.bieberlabs.com/wordpress/archives/2004/11/30/using-svk
  • Part 2: http://www.bieberlabs.com/wordpress/archives/2004/12/31/svk-distributed-version-control-part-ii
  • Part 3: http://www.bieberlabs.com/wordpress/archives/2005/01/08/svk-distributed-version-control-part-iii
  • Workflow notes: http://www.bieberlabs.com/wordpress/archives/2005/03/19/explaining-the-svk-workflow
• The "SVK book": http://svkbook.elixus.org/nightly/en/index.html
• SVK Guide: http://wiki.sourcemage.org/Svk_Guide
• svk-dev mailing list: http://lists.bestpractical.com/cgi-bin/mailman/listinfo/svk-devel