Veracity 2.0 Release Notes
Veracity 2.0 is now available for download.
This release includes many performance and stability improvements in the open source core. We're also pleased to announce the launch of our Veracity hosting service, onVeracity.com.
The public Veracity repository has been updated. It now requires a 2.0 binary to clone.
Private Repository Hosting
Hosting for private repositories is now available at onVeracity.com.
- Securely host your version control, work items, wiki, and build tracking database.
- Free accounts support up to five users. Paid accounts are $20 per user per month.
- A Veracity 2.0 client is required to use onVeracity.com.
- See the FAQ for more information.
New Core Features
- The repository format has changed to improve database index and query performance.
- Advisory file locks are more reliable, and are now available from Tortoise.
- Commits can now be linked to a Veracity work item from Tortoise.
- The web interface has been updated with a new look.
- Clone has been revised to do less I/O, resulting in much faster performance for large repositories.
- Push clone has been implemented.
- The history of a wiki page and the ability to compare revisions are now available.
- Veracity Sync (a utility for Windows) now allows multiple instances with a settings profile specified on the command line, e.g. '
- The command line interface for resolve has been simplified. Details are available in
vv help resolve.
- Client SSL support has been added.
Noteworthy Bug Fixes
- Tortoise client performance is significantly better on systems with numerous working copies. (details)
- An intermittent issue in the Tortoise settings dialog that could prevent the the current user from being saved has been fixed. (details)
- Several fixes have been made in
- A case where push could silently fail from the Tortoise client has been fixed. (details)
- Working copy ignore patterns beginning with
@/are now honored. (details)
- Several bugs related to the interaction between branches and locks have been fixed. (details)
- This working copy bug has been fixed.
- Committing with an "unknown" user name is now prevented. (details here and here)
- The sort order for work item priorities has been fixed, though upgrades from 1.x require a manual fix. (details)
Notes for Veracity 2.0 Beta Users
The 2.0 beta release on Windows will need to be uninstalled before the final build can be installed. Your repositories and configuration data will remain intact.
Notes for Veracity 1.x Users
Teams using Veracity should all use the same major version. 2.0 clients only work with 2.0 servers and 1.x clients only work with 1.x servers. Teams should move to 2.0 together.
- Upgrading from Veracity 1.x requires repositories to be converted to the new format. (Working copies have not changed.) After installing 2.0, type '
vv upgrade' at a command prompt to convert all local repositories.
- 1.x advisory file locks are not upgraded. Files should be re-locked following the upgrade.
- The priority sort is backwards for work items in repositories upgraded from 1.x. Follow these instructions to fix it.
- If you want to revert to 1.x for some reason, you can. Follow these instructions.
- The names of repositories, branches, tags, stamps, and users are more restrictive in 2.0.
- Names cannot exceed 256 characters in length.
- These characters are now disallowed:
- Repositories with now-invalid names must be renamed before they can be upgraded to the 2.0 format.
- Existing branches, tags, stamps, and users with now-invalid names will continue to work, but new items cannot be created with similar names.
- If you installed Veracity 1.0 on a Mac, you may need to manually correct a configuration. In /etc/veracity.conf, change
The following operating systems have been tested:
- Windows XP SP3 32-bit
- Windows Server 2003 SP2 32-bit
- Windows Vista SP2 32 and 64-bit
- Windows Server 2008 R2 Standard SP1 64-bit
- Windows 7 SP1 32 and 64-bit
- Snow Leopard
- Mountain Lion
- Ubuntu 11.10 Oneiric 32 and 64-bit
- Ubuntu 12.04 Precise 32 and 64-bit
Veracity works best in one of the following browsers:
- Chrome or Chromium 18+
- Firefox 11+
- Safari 5+
- Internet Explorer 9 (IE 8 also works, with some aesthetic issues)
Known Issues in Veracity 2.0
- Moving or renaming parents of working copies is sometimes prevented by the Tortoise client. (details)
- Windows allows a small, fixed number of icon overlays in Explorer. People using both Dropbox and Veracity's Tortoise interface will not be able to see Veracity's file lock overlay, which indicates files that you have locked.
vv upgradestops when it encounters a repository name that does not conform to the new naming restrictions (see Notes for Veracity 1.x Users above). If this happens, rename the offending repository and re-run