Fortress 1.0.1 Release Notes

A collection of information about Fortress, including solutions to common problems.

Moderator: SourceGear

Post Reply
jeremy_sg
Posts: 1821
Joined: Thu Dec 18, 2003 11:39 am
Location: Sourcegear
Contact:

Fortress 1.0.1 Release Notes

Post by jeremy_sg » Thu Jun 14, 2007 11:00 am

SourceGear Fortress 1.0.1 is a maintenance release for Fortress 1.0. If you have not upgraded to Fortress 1.0 version, see http://www.sourcegear.com/fortress/releases/1.0.html for more information.

Known issues:

There are still issues which prevent using projects in the Visual Studio 2005 IDE Client which are bound to source control in a solution which is not bound. If you use this configuration, please remain on the 2003 compatible client until these issues have been resolved.

Installation Notes:

If you are converting a Vault or Dragnet installation, you must uninstall those products before installing Fortress. When uninstalling, choose to keep the databases.

In order to convert an installation of Vault and Dragnet to a Fortress installation, both the sgvault and sgdragnet databases must be on the same SQL server instance. Use the detach and reattach functions in SQL server to move databases if necesarry. It is recommended that you convert to the latest version of Dragnet before convert to Fortress.

For users converting from an installation of Vault only, the Fortress work item tracking database will be automatically created.

It is not recommended to convert an installation with only Dragnet. Install Vault 3.5.2 beside your Dragnet installation and convert them as normal.

Changes From Vault 4.0.1:

* An upgrade from Vault and Dragnet was causing the user with Vault userid 2 to have restricted access to Fortress projects.
* The sort order of items returned on the My Recent page was wrong.

Client/Server Version Compatibility:

It is always recommended that your client and server versions match exactly (e.g., a 1.0.1 client should be connecting to a 1.0.1 server). 1.0.x clients are able to communicate with any 1.0.x server, but specific bug fixes will not work correctly if they required both client and server changes.

Post Reply