This file lists the recent defects fixed in Serena Mover. For information on using the current release of Mover, see readme.enUS.html.
When you deploy a Dimensions baseline, you can refine your selection by filtering on multiple item types. However, in previous releases, filtering on multiple items types resulted in a deployment failure. This has been fixed.
In previous releases Mover did not fully support the Secure Sockets Handling (SSH) protocol; it was still necessary to provide a user name and password. This has been fixed; you can not use a SSH key to pass in user names and passwords.
In previous releases, the deployment ID returned by the Mover Command Line was off by one number. This has been fixed.
In previous releases, Mover did not provide an audit log of project activities, such as user activity. This has been added in this release. You can now see what users have logged in and out, and when deployments have taken place.
When you deploy files from Version Manager, Mover creates parent folders for those files based on the project structure in Version Manager. This can result in an incorrect file structure on the deployment target. This has been fixed.
In previous releases, deploy maps are not run in the sequence in which they are listed in a package. This can cause problems, especially when there are dependencies on the deployment order for builds to run successfully. This has been fixed in this release.
After deploying binary files via FTP, they approximately doubled in size on the target server. This has been fixed.
When you browse for a Dimensions workset (now called project) to deploy, the workset name is not added to the Workset name field.
With Dimensions CM 10.1, when you browse to select a workset (now called project) to deploy, only your default workset is visible. All available worksets should be visible.
The Java Runtime Environment (JRE) included with Mover must be upgraded to version 1.4.2 in order to support changes to Daylight Savings Time.
When you created a new source from the Mover command line interface using the CreateSource command, the filter argument was ignored. As a result, the source was not created with a filename filter (such as *.doc), and instead defaulted to *. This has been fixed.
Previously, users could delete activity logs for deployments they scheduled and executed. In addition, project administrators could delete any activity log within a project. In order to ensure the audit trail of deployments required for regulatory mandates such as Sarbanes-Oxley, an additional project level permission called Delete activity logs has been added. This privilege allows administrators to control who, if anyone, has permission to delete activity logs.
Start date, package ID, name, description, and username data have all been added to the beginning of a full activity log file. This ensures an accurate record of the person who started the deployment, even if the deployment was started by someone different than the person who scheduled the deployment. The following is an example of the new information in the Mover 2.0.1 activity log:
--------------------------------------------------------------------
Serena Mover
--------------------------------------------------------------------
Start date: Dec 22, 2004 8:55:52 AM
Pkg Id: 26
Package: Deploy PAYROLL
Description: PAYROLL:BL_DEV_REL_1_B
User Id: barbie
--------------------------------------------------------------------
Although the Formatted Dimensions release command field in a Dimensions source was able to accept several hundred characters, the field previously only displayed the first 84 characters of a command. The field has been expanded to display 312 characters.
In order to improve display speed and simplify the review of current activity logs, a time filter has been added to the activity archive view. This allows users to limit the records viewed to a specific number of previous days. The new filter defaults to displaying logs from the last 7 days, but includes the following options: 1, 7, 14, 30, or All days.
Previously, when cloning Version Manager or Dimensions sources, the deployment settings for the cloned sources was not stored, requiring you to modify and re-save the clones with the correct settings. This has been fixed.
Available packages and sources, which are listed on the Deploy dialog box and on the Add Deploy Map dialog box, were not listed alphabetically. This has been fixed.
Long commands were not formatted correctly in the Edit Package dialog box. This has been fixed.
You could not previously export / import users and groups from one installation of Mover to another. This has been fixed.
From the System | Users and Groups view, you can now export all user and group information to an XML file, and then import them to another installation of Mover. See the readme file for details.
Copyright © 2001-2006 Serena Software, Inc. All rights reserved.