3.0.5 Release Notes

[dan]

Changes for 3.0.5
The following features and changes have been included in the 3.0.5 release:

Client Only Changes
· Edited files within inherited working folders were sometimes not added to the pending change set after an edit, depending on the program that was editing the file. These files should now appear in the pending change set after an edit.
· Non-Mergable files are now checked out exclusively when the checkout dialog is not shown.


--------------------------------------------------
<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.