3.0.6 Release Notes

[dan]

The following features and changes have been included in the 3.0.6 release:

<b>Windows GUI</b>
· When a connection is lost, more details on the actual error are reported.
· Intermittent cases of a checkin undoing the checkout have been resolved.
· Working folder is now scanned before doing a checkin from the context menu of the folder.
· Checked in files are no longer unnecessarily backed up.
· Get Repositories button in the Edit Profiles dialog now respects proxy settings.
· Default credentials are now provided for proxies.
· Pending Change Set is now accurate after hundreds of files are modified at the same time.


<b>Merge Branches Tool and Diff/Merge Tool</b>
· · Merge Branches no longer throws an exception when the origin has been renamed or moved and the working folder assignment is not inherited.
· Default comments for merge branches now include only those transactions that were included in the merge.
· Merge Tool no longer throws an exception when two files have a partial match at the beginning of the file and one of the files has fewer lines than the patch.

<b>Command Line Client</b>
· Obliterate command now available
· Now honors proxy settings, as well as proxies that require authentication
· Allows specifying begin/end labels for history queries
· Allows specifying user and actions to exclude in history queries
· Outputs label name in history output
· Allows repository deletions
· Allows removing local copies of deleted files during Gets

<b>Server Only</b>
· Obliterate performance has been improved
· Rollback no longer allowed if file is exclusively locked.


<b>Client/Server Version Compatibility</b>
It is always recommended that your client and server versions match exactly (e.g., a 3.0.1 client should be connecting to a 3.0.1 server). 3.0.x clients are able to communicate with any 3.0.x server, but specific bug fixes will not work correctly if they required both client and server changes. 3.0.x clients and servers are <b>not</b> compatible with 1.x or 2.x clients and servers.

<b>Upgrading From Previous Versions</b>
It is recommended that you backup your Vault database prior to an upgrade. This can be done from either the Vault Admin tool, or the SQL Enterprise Manager tool.

To upgrade from a previous installation of Vault, simply invoke the new installer, and choose the same options that were selected when Vault was previously installed. Program files and configuration settings will be automatically updated to reflect the upgrade. Note that the server installation will not delete your database unless you explicitly tell it to.

You may also safely uninstall Vault first, and then install the upgrade. As with installation, an uninstall will not delete your database unless you explicitly tell it to.