3.1.3 Release Notes

[dan]

3.1.3 is a maintance release for 3.1. If you have not upgraded to any 3.1 Vault version, see http://support.sourcegear.com/viewtopic.php?t=4294 for more information.

The following changes are included in this release:

GUI Client Only
· History actions dialog no longer displays unnecessary radio buttons.
· Adding a file that is part of an added subfolder that has the same name as a file in the root folder being added to will now be added correctly.
· Labels applied to historical versions of a folder are now displayed with the folder version, not the date the label was applied.
· Merge Branches no longer scans all working folders on exit of the wizard.
· Help link on Cache/Backup Locations Options dialog now goes to correct page in help.

IDE Client
· Bug tracking now gets updated properly when project is using SCC, but solution is not.
· IDE now autogenerates comments (such as "item: XX - description") when a bug is associated with an IDE checkin, so that it works just like the GUI client.
· Bug IDs can now be entered for Fogbugz installations without displaying an error.


Web Client
· Can now link to a history page when the history path contains spaces.
· Folder and file names with special characters are now displayed correctly.

Server Only
· EOL now set properly for Gets on Mono systems.
· Shadow Folders can now use an impersonated user that does not have access to the registry.
· Performance has been improved when applying security rights to a folder with tens of thousands of versions.
· Corrected group security right permissions in scenarios where a different user was denied access in one of the folder's ancestors.

Installation
· Installers now detect the previous installation path and uses it on an upgrade.
· Upgrades from pre-3.1 now handles databases that use case-sensitive collation.


<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.1.x clients are able to communicate with any 3.0.x or 3.1.x server, but specific bug fixes will not work correctly if they required both client and server changes. 3.1.x clients and servers are not 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.

Important: If you are upgrading from a pre 3.1 version of Vault, the server installation will take longer than normal because the database needs to be converted to a new format.

Also, the client install will upgrade client cache files to a new format if you are currently on a pre 3.1 release. This will not affect upgrade times, but also will not allow you to revert back to a pre 3.1 client without losing client state information.