This document contains information about defects fixed in ChangeMan DS, and new features and functionality. For information on installing and using the current release of ChangeMan DS, see the readme file and ChangeMan DS documentation.
NOTES:
Part 1: Release Highlights
Part 2: License Utility for ChangeMan DS
Part 3: Fix Log
Part 4: Legal
Part 1: Release Highlights |
The following Release Notes for ChangeMan DS 5.7.1 provide an overview or commentary about important functionality in the release. Please refer to product documentation for specific details on functional operations.
A new wizard is provided to make it easy to restore files that have been deleted from the ChangeMan DS repository. When a file is restored, its associations with specific directories or areas and their histories are also restored, as are attachments to projects and frozen releases. The following backups must be available to support the restore operation:
NOTE: Support is not provided in the current release to restore entire areas, projects, frozen releases, Make configurations, or Make histories as objects.
It is now possible to alter the default behavior on the Transfer dialog by changing a setting in the changeman.ini file for the Windows client.
As shipped, the changeman.ini file sets the Transfer dialog default to a full check out with editing enabled on transferred files. To transfer files in read-only mode without a full check out, users must check the read-only checkbox in the Transfer dialog.
For users who perform many read-only transfers and relatively few full check outs, a new option has been added to the [TransferPrompt] section of the changeman.ini file. Set the parameter value to ReadOnly=1 to force all transfers to execute in read-only mode, regardless of the checkbox setting in the Transfer dialog. Set the parameter value to ReadOnly=0 to resume normal check out transfer behavior.
NOTE: The changeman.ini file is used with the Windows client only. If you want to enforce read-only transfers throughout your organization, you must modify the changeman.ini file on all client machines running Windows.
It is now possible to selectively enable an "Edit" privilege for users who have access to an End User Area. Users who do not have edit permissions for an area can still view its contents if they have access.
All users who currently have access to an End User Area under ChangeMan DS 5.7 will by default have both viewing and editing privileges for that area after upgrading to ChangeMan DS 5.7.1. You must turn off the edit privilege for those users you wish to restrict to read-only access.
A new authorization option on the server allows you to restrict users to view-only access to a project.
When checking out a file to a folder where the same file already exists, a warning is reported and you can now choose to not overwrite the file.
In a development environment with a large number of projects and areas, the apparent time to create a new project can degrade. This occurs because the GUI interface must download the entire list of current projects and areas from the server to the client before displaying the newly created project in the project and area file trees.
Formerly, the Command Line Interface (CLI) also downloaded the entire project and area list to the client when creating a new project. In ChangeMan DS 5.7.1, the CLI project create function now downloads just those project and area properties needed to create the new project. Customers with a large number of projects and areas should see significant performance improvements when creating new projects using the CLI.
ChangeMan DS 5.7.x does not support Guardian/OSS (HP NonStop)
ChangeMan DS 5.7.x does not support MPE/iX (HP3000)
Installation of shared Metadata repository between ChangeMan ALM and ChangeMan DS 5.7.x is not supported
Part 2: License Utility for ChangeMan DS |
License keys for ChangeMan DS are issued based on specific quantities of users and Communication Agents. To ensure your new license key is issued for the correct component quantities, Serena has created a license utility which must be run prior to product installation to ensure the correct keys are created. This utility can be run against ChangeMan DS version 5.4.1 or later.
To run the license reporting utility:
licensereport -user:<admin> -host:<host>
where:
<admin> is the ChangeMan DS user ID for a ChangeMan DS administrator
<host> is the hostname or IP address of the ChangeMan DS Main Server
A report is displayed stating the ChangeMan DS server name and IP address, the ChangeMan DS version and date, and the number of licensable users and Communication Agents.
Part 3: Fix Log |
The following tables list defects fixed in ChangeMan DS 5.7.1. Customers can use the Solution ID in the first column of each table to look up details for a given fix. Solutions are available in the Knowledge Base on the Serena Online Support (SOS) Web site at http://support.serena.com.
Solution ID | Description |
5001206 | Ability to create subdirectories in areas without 'allow directory creation' |
5001207 | Ability to see the patch or fix level of DS |
5001208 | Relative path is not set when dragging/dropping from a production area |
5001217 | Distribution of file to End User area via GUI deletes the existing file |
5001227 | Merge of VB projects results in new components added to branched project |
5001235 | Cannot check in after upgrade, required to provide TeamTrack item ID |
5001237 | DS merge failure dialog contains bad grammar |
5001238 | Interactive merge to development fails because WORDDIFF cannot open common ancestor |
5001240 | Option in the Transfer dialog to always set read-only flag |
5001242 | Ability to set the modification time of a file |
5001243 | Area rename scripts remove files from source control |
5001252 | Files are not deleted after a transfer on MPE communication agents |
5001256 | Ability to restore single files, directories, or entire areas along with their history |
5001257 | User-friendly capability to lock down End User area |
5001258 | Provide the ability to create a 'read-only' user that can look but not touch |
5001259 | Builds crash with message 'Exceeded max number of connections' |
5001262 | Project-level approvals do not work |
5001264 | Builds - 'Make' history not showing any results as to why it failed |
5001265 | Project view of attachments doesn't refresh file status automatically |
5001267 | Ability to check out files without overwriting the development copy |
5001273 | Starting 'Starserv' gets error message on SCO Unix machine |
5001274 | Able to create more than one area using the same path and the same host name |
5001277 | Builds - Relative path for 'Make' procedure in frozen release gets truncated to 50 characters |
5001278 | File tree shows incorrect check-out timestamp information |
5001279 | '&' in filename causes $VCSFILE in area script not to be initialised |
5001281 | Error message should be more user friendly for approvals when invalid characters are used |
5001282 | Builds - Ability to set target/dependency path to subdirectory of Area path |
5001285 | Performance - Optimize area administration |
5001291 | AIX - Ability for DS to use /TMPDIR instead of /tmp |
5001297 | DS changes Unix security that was set in an implementation script |
5001298 | Deleting DS areas allows all users to see all other areas until area is deleted |
5001302 | Comparing files and selecting print preview results with 'diff.exe' generates memory errors |
5001303 | When web server is configured to use IIS virtual server, it generates Java errors |
5001310 | Branching a project does not set relative path |
5001312 | DS 5.6.1 does not contain 'starserv' for USS |
5001316 | Directories containing a period (.) or underscor (_) on USS render old revisions unreadable |
5001319 | Starserv process does not start |
5001320 | Implementation script executes only once when pending is set |
Solution ID | Description |
5001236 | POA - Default security settings do not get inherited by individual application or package when changed |
5001280 | POA - Creating a package name with more than 50 characters results in error 'Can't find frozen release' |
5001284 | POA - Package installation history shows time set to 12AM default |
5001321 | POA - Package approval hangs if DS group is deleted |
Solution ID | Description |
5001214 | Folder ../DS/Client/Samples contains DCM examples instead of CMNXFER examples |
5001209 | CLI - Unable to create groups using the audit file permissions |
5001210 | CLI allows an invalid relative path to be set |
5001211 | CLI - Creating an area with the 'addauth' parameter does not define the user via the GUI |
5001212 | CLI - CMNXFER - Second checkout does not work using the answer values |
5001213 | CLI - CMNPROJ returns 'Command completed successfully' when adding a file to a nonexisting release/version |
5001224 | CMNPROJ - Permissions not added when creating a project |
5001225 | Performance improvements with large number of projects and areas |
5001239 | CLI - Command syntax does not show additional login switches |
5001241 | CLI - CMNPROJ 'actlist' lists Version '0' for files that are in subareas |
5001263 | CLI - Permission file templates are incorrect |
5001266 | CMNPROJ - Error 'Unable to get release info' when updating frozen release with file version and description |
5001268 | CLI - Frozen release name gets truncated after 50 characters |
5001270 | CLI - CMNAREA does not remove the group from authorization list |
5001272 | VCM_MAKE process hangs |
5001283 | Performance recommendations for VCS_DOC |
5001292 | CLI - Ability to prevent users from editing End User area |
5001293 | CLI - CMNPROJ displays error 'Unable to get release information' when trying to update file |
5001299 | CRCUpgrade - Fails with message 'Can't perform gethostname function' on Unix platforms |
5001300 | CMNPROJ - Core dumps when getting large project list |
5001301 | VCS_DOCUMENT and VCS_SCHEDULE crash after hot backup of Oracle database |
5001304 | CRCUpgrade utility used on UDB/DB2 database gives errors |
5001306 | CLI - User validation does not take place iIf user has 'Trust Network Login' |
5001309 | CRCUpgrade utility results in core dump when two files in an area have the same name |
Solution ID | Description |
5001255 | WSAD script execution should support project-level execution |
5001275 | WSAD - Plugin does not revalidate screen |
5001290 | WSAD - Copying frozen release to a local workspace with forward slash or backward slash in name gives errors |
5001296 | WSAD - The current method of synchronizing offline files should match our documentation |
5001308 | WSAD - Synchronizing identical files displays as incoming changes |
5001314 | WSAD - Refactoring with Eclipse 3.0 gives error 'Team provider refused file modification' |
5001318 | WSAD - Performance issues when doing synchronization |
Solution ID | Description |
5001307 | .NET - Branching a project gives error |
Solution ID | Description |
5001232 | JBuilder crashes when 'Pull project from DS' and SCC provider is SourceBridge |
Solution ID | Description |
5001228 | DS Java client - Clicking on 'Exit' button on Serena toolbar gives error |
5001311 | DS Java client - Changing a user's password returns error |
Solution ID | Description |
5001234 | DS Web client users can access certain functionality with no password |
5001295 | DS Web client - Audit trail pending approval list shows nothing to approve |
Part 4: Legal |
Copyright © 1998-2005, SERENA Software Inc. All rights reserved.
This document, as well as the software described in it, is furnished under license and may be used or copied only in accordance with the terms of such license. Except as permitted by such license, no part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, recording, or otherwise, without the prior written permission of SERENA Software, Inc. The content of this document is furnished for informational use only, is subject to change without notice, and should not be construed as a commitment by SERENA Software, Inc. SERENA Software, Inc. assumes no responsibility or liability for any errors or inaccuracies that may appear in this document.
Serena and ChangeMan are registered trademarks of SERENA Software, Inc. All other products or company names are used for identification purposes only, and may be trademarks of their respective owners.
Portions of this product are redistributed unmodified in binary form from the Eclipse Organization. Source and binary code is available from http://www.eclipse.org/.
Portions of this product are copyrights of other corporations or individuals, as follows:
Copyright © Caldera International Inc. 2001-2002. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1. Redistributions of source code and documentation must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
3. All advertising materials mentioning features or use of this software must display the following acknowledgement:
This product includes software developed or owned by Caldera International, Inc.
4. Neither the name of Caldera International, Inc. nor the names of other contributors may be used to endorse or promote products derived from this software without specific prior written permission.
USE OF THE SOFTWARE PROVIDED FOR UNDER THIS LICENSE BY CALDERA INTERNATIONAL, INC. AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL CALDERA INTERNATIONAL, INC. BE LIABLE FOR ANY DIRECT, INDIRECT INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Copyright © 2003 Todd C. Miller (Todd.Miller@courtesan.com)
Permission to use, copy, modify, and distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.
THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
Sponsored in part by the Defense Advanced Research Projects Agency (DARPA) and Air Force Research Laboratory, Air Force Materiel Command, USAF, under agreement number F39502-99-1-0512.
Copyright © 1991, 1993
The Regents of the University of California. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
3. Neither the name of the University nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
End Release Notes