Veracity Changelog
What's new in Veracity 2.5.0.11065
Sep 26, 2014- Noteworthy Changes:
- The working copy code has been overhauled to be faster and more reliable.
- After upgrading to 2.5, users must checkout new working copies. Commit any changes before upgrading.
- In the web interface, you can now search for changesets from the branch page, yielding their relationship to the branch.
- You can now manipulate branches from the web interface.
- On Linux, Veracity now uses the platform SpiderMonkey JavaScript interpreter package (libmozjs185-1.0).
- Fixed a bug in 2.1 where a server under heavy load could serve an invalid clone, leading to a zlib error on the client.
- Made several fixes related to displaying Unicode characters on Windows. In particular, error messages and the cat command are better behaved.
New in Veracity 2.1 (Sep 26, 2014)
- NEW FEATURES:
- Command Line:
- Native Subversion import support has been implemented. (details)
- The new merge-preview command provides changeset-centric history queries. See vv help merge-preview for details.
- "Fast forward" merges (merges that don't require an actual merge) are now handled nicely by vv merge and the tortoise app.
- Web:
- There is now a branch page with a simplified, branch-specific view of source history.
- The changeset page has been simplified. Merge changesets now include a graphical summary of the merge.
- Work item descriptions now support Markdown syntax.
- Search is much faster, includes wiki pages, and has better-formatted results.
- The milestone settings page has been redesigned.
- The wiki now has a link syntax for branch head, version control tag, and saved work item filters. See the wiki help for details.
- NOTEWORTHY BUG FIXES:
- Command Line:
- Several fixes were made in fast-import and fast-export.
- Tortoise (Windows Only):
- Moving and renaming working copies is now well-behaved. (details)
- Lots of usability and performance issues were improved.
- Web:
- You can now change the name and description of released milestones.
- Confirmations when navigating away from an edited page are now more consistent.
- The estimated completion date on the Burndown Chart now correctly corresponds to the chart in all cases.
New in Veracity 2.0 (Sep 26, 2014)
- 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.
- 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. 'vvwinsync.exe my-sync-settings'.
- 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 fast-import and fast-export.
- 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)