REMINDER: The Support Staff at Visible Systems would like to remind users that releases of Razor prior to 4.3 are no longer supported. Please upgrade your site at your earliest convenience. Detailed instructions follow. Remember to follow ALL the separate upgrade steps where appropriate. ************************************************************************** ************************************************************************** ** ** ** MANDATORY PATCHES ** ** ** -------------------------------------------------------------------------- ** ** ** !!!! HPUX 10.x & 11.x USERS !!!! ** ** ================================ ** NOTE=> All users of HPUX 10.x and 11.x need to install one of the following patches to correct a problem with SCCS handling the year 1999. This problem will be evident when attempting to modify files archived in the Razor database (i.e. modify issues, checkin files, edit threads): HPUX PATCH ---- ----- 10.01 PHCO_16250 10.10 PHCO_16251 10.20 PHCO_16252 11.0 PHCO_16253 If you or your system administrator have additional questions, please contact your HP representative. -------------------------------------------------------------------------- ** ** ** !!!! HPUX 10.2 USERS !!!! ** ** ========================= ** NOTE=> All users of HPUX 10.2 need to install an HP supplied patch (PHCO_13084) to correct a problem related to how 'awk' processes multi-tab entries. -------------------------------------------------------------------------- ** ** ** !!!! IRIX 6.2 and IRIX 6.3 USERS !!!! ** ** ===================================== ** NOTE=> All users of IRIX 6.2 and IRIX 6.3 need to install an SGI supplied patch to the /usr/bin/delta program. The official IRIX 6.2 patch number is SG0001643. For IRIX 6.3 users as well as those IRIX 6.2 users who may not have ready access to the patch, a copy of the 'delta' program is available via anonymous ftp from ftp.tower.com in the file: IRIX/Patches/delta ** ** ************************************************************************** !!!! Solaris 2.5 OR HIGHER USERS !!!! ====================================== NOTE=> If you are installing on a Solaris 2.5 or higher machine (SunOS 5.5 or higher), "/usr/dt/lib" should be installed. ************************************************************************** ************************************************************************** ** ** ** UPGRADE NOTES ** ** ** -------------------------------------------------------------------------- ** ** ** !!!! IF UPGRADING FROM v3.4 to v4.2 or higher!!! ** ================================================ ** NOTE=> Existing users must use the script 'update_db_3.5' to bring their database up to date. To use this script, make sure that you have sourced the rz_prep file to set the proper Razor environment parameters and then simply execute update_db_3.5. The files in the Info directory for each group in the database will be udpdated. The original Info directory will be preserved as a backup and may be removed when you are satisfied that the changes were implemented. The name of the backup directory will be output when the script completes. NOTE=> You must also follow the 3.5 to 4.x instructions as well as the pre-4.1d to 4.x instructions. -------------------------------------------------------------------------- ** ** ** !!!! IF UPGRADING FROM v3.5 to v4.2 or higher!!! ** ================================================ ** ** ** NOTE=> You must run the new script update_state_dates in order to convert your Issues STATE entries to 4 digit year values. This script will only need to be run one time and will update your Info files. Backup copies of all Info files will be made by the script as a precaution. NOTE=> In order to support file renames, the Thread_script_template.sh has been modified. Users MUST place this file (located in $RAZOR_HOME/templates/Threads_tables_templates) into the Tables directory of each Threads group. NOTE=> Modified the following scripts to execute much faster. The name flag MUST be added to the file: $RAZOR_UNIVERSE_DIR/DOMAIN_01/++ISSUES++/Tables/Reports for each entry which references one of these scripts: rz_issue_summarize rz_issue_display_titles rz_issue_print_titles rz_issue_summarize_short rz_issue_print rz_issue_print_short rz_issue_status.rpt NOTE=> You must also follow the pre-4.1d to 4.x instructions. -------------------------------------------------------------------------- ** ** ** !!!! IF UPGRADING FROM pre-4.1d TO 4.2 or higher !!!! ** ** ====================================================== ** ** ** NOTE=> If you are currently using a release of Razor prior to 4.0, you must FIRST follow the appropriate instructions (3.4 to 4.x and/or 3.5 to 4.x). ** The following steps should be followed PRIOR to starting the upgrade process: o Review these RELEASE_NOTES in their entirety. o All files must be checked in. This step is MANDATORY due to major changes to the archival scheme introduced with 4.1d. Also, please make sure that all Archive directories are owned by the owner of the database and have write permission for the owner of the database. We don't normally require that all files be checked in prior to upgrading, however, due to the nature of the changes to the version control system for this release users MUST have all files checked in. o Make sure that you have a backup of all Razor databases. o Exit all Razor tools (issues, versions and threads) o Take down all database servers o "kill" the Razor license manager (razor_lm) ** Invoke the upgrade script: o Upgrade your current release by invoking the script Razor_/scripts/rz_install ** Invoke the following scripts as appropriate: o For EACH database, the owner of the database must run Razor_/scripts/update_db_vcs The following updates will be made to your existing database(s): - $RAZOR_UNIVERSE_DIR/rz_db_exec will be replaced by $RAZOR_UNIVERSE_DIR/bin//rz_db_exec. This change easily accommodates multi-platform access to the same database. - Current threads groups will be renamed from ::Threads to ##Threads. - This script will determine which archive engine is currently in use for each database. If an empty folder (subdirectory) is encountered, the script will query the user for which archival engine to use. The response will be used for ALL subsequent empty folders. o For EACH database that is using remote database synchronization, the owner of the database must update the primary (master) and ALL secondary (slave) sites by running Razor_/scripts/rz_install_remotes. o If you are submitting new issues via e-mail and have customized the rz_mail_issue_catcher script, we recommend that you save a copy of your current script (rename to rz_mail_issue_catcher.orig) prior to executing the next step. o For EACH database and EACH issues group within that database where new issues are submitted via e-mail, the owner of the database must run Razor_/scripts/rz_install_email_catcher. o For EACH database that is using the remote e-mail checkout/checkin capability, the owner of the database must run Razor_/scripts/rz_install_email_query. ** Update your current IssueWeaver installation by invoking the script Razor_/scripts/rz_iw_install. o If you are currently using a release of IssueWeaver prior to 4.1c.04, we encourage you to review the Release Changes in the document RELEASE_NOTES.old for an overview of the enhancements made to this product. This document is located in the directory 'doc' within the Razor installation. ** Ready to run... o Restart the Razor license manager ( razor_lm & ) Refer to Chapter 2 of the manual, "Installing product upgrades", for general upgrade instructions. If upgrading an NT Server installation, refer to Appendix G, "Doing the install". Please refer to the UPGRADE NOTES outlined above for specific instructions. ----------------------------------------------------------------------- *********************************************************** Changes for version 4.3a.06 *********************************************************** - In Issues, correct problem with multiple carriage returns creating large spaces in text panes. *********************************************************** Changes for version 4.3a.05 *********************************************************** - Razor now integrates with MetricCenter. MetricCenter is now available as an add-on tool to Razor. MetricCenter will enhance your reporting capabilities by providing additional metrics. For additional information, please contact the Sales Department at sales@distributive.com. V: 800-779-6306 http://www.distributive.com - In Versions, corrected a problem with the merge function where the number of conflict regions were not computed correctly. - Add capability to print from the Browse window in Versions and print in the Commands output window for Issues, Versions, and Threads. - Correct the file introduction process to handle Apply and OK if selected simultaneously. - Modify file introduction processing so database does not terminate when client is terminated during the file introduction process. - Correct Report reading/writing of filters to handle more than 32 attribute values. - Correct problem with Issues and switching databases via the Databases menu in Windows2000. - Correct problem with Vcs files when making a new Issue group in Windows. - For e-mail submission of issues, updated the Permissions and Access_list file templates to include e-mail entry of issues is done as Razor user 'daemon'. - Correct typo in rz_html_utils script. - Correct rz_issue_print script when user has set noclobber. - Update the rz_toolbox and spill scripts to work in Windows. - Correct problem with the Windows administrator not being able to start a database created by a non-system administrator. - In Windows Admin GUI, removed RazorDB from database name. - For Windows NT/2000, enable sending of e-mail upon state changes of issues and submission of error logs to support. Outlook and Outlook Express are supported. - On the PC and UNIX clients (Issues, Versions, Threads), modify the path statement to allow the user to input the Windows or UNIX path to the database. - When starting the Razor Admin GUI, a popup notice will be displayed to inform the user when license keys have not been installed and when a database has not been installed. - Modify Razor SCC functionality to "get read-only" copies of files and to "get latest version" of files. - Improve the Razor SCC interface with Rational Rose. - Modify Razor SCC to prevent accidental loss of data while performing the "Get Latest Version" operation on files. - For Razor SCC, allow mapping for existing Visual Studio projects from Razor to other machines. - For the Report Generator, corrected the problem with multiple delimitors in export files and added a carriage return between the attributes and the first line of data. - Changed the warning message from "No tokens available" to "No Licenses Available". - In the Demo database, correct the path to the must_have_issues_at_state script. *********************************************************** Changes for version 4.3a.03 *********************************************************** - For IssueWeaver, added support for "system" filter files. The system filter files (sys_filter..default, sys_filter.. in directory $RAZOR_UNIVERSE_DIR/Weaver/user) provide the Razor system administrator with a means of limiting the issues available to an individual user. For additional information, see README.IssueWeaver. *********************************************************** Changes for version 4.3a.02 *********************************************************** - Warning: The encryption of transmitted information is disabled for the SunOS 4.1.x versions of Razor. This affects anyone using Razor remote from a SunOS 4.1.x client to any server platform and also from any client platform to a SunOS 4.1.x server. *********************************************************** Changes for version 4.3a.01 *********************************************************** - Updated the Razor command-line interface to allow for modification of Issue attributes via the command-line, Issues create.apply after script, or Issues modify.apply after script. The syntax of the new command is as follows: razor -c modify_issue -f -g -a : For TIME_STAMP attributes must use same format as specified in the Issue Attribute file. For TEXT_PANE attributes must specify attribute value as the full-path to the file to replace (Writeable TEXT_PANEs) or append to (AppendOnly TEXT_PANEs) current text pane contents. For X_OF_MANY attributes must specify attribute value(s) as a comma-delimited list (without embedded spaces). For CHECK_BOX attributes valid attributes are: 0,1. For TEXT_FIELD attributes specify text strings with embedded spaces using double-quotes. Command does NOT support modification of Issue attributes of type STATE or LABEL. The STATE attribute type may be modified via the `promote_issue` command. The LABEL attribute is not associated with a single issue. Rather, it is applied to all issues within a given Issue control group. *********************************************************** General Release Changes for version 4.3 *********************************************************** - Incorporate the exit.apply function to the Issues, Versions and Threads Actions tables to facilitate the use of a BEFORE script when exiting Issues, Versions and Threads. - Improved cleanup of 'tmp' files when Razor is exited. - Added the ability of Versions, when autodetect is selected, to recognize files containing extended ASCII characters as text files. - Added logic to insure that only one server process is run against a database. - Modified the scripts rz_issue_print(.sh), rz_summarize_issue(.sh), rz_issue_summarize_file(.sh) to use the correct text pane titles. The following are examples of running each script from the commandline: --) rz_issue_print and rz_issue_print.sh To run this you have to include the issue # with a -f flag ( e.g. rz_issue_print -f I..2-025 ) --) rz_issue_summarize and rz_issue_summarize.sh To run these you have to touch a file inside of your Info directory. Then add the issue numbers that you would like to summarize to this file. ( e.g. cd $RAZOR_UNIVERSE_DIR/DOMAIN_01/$RAZOR_GROUP/Info/ touch file1 echo I...2-045 >> file1 echo I...2-025 >> file1 $RAZOR_HOME/scripts/rz_issue_summarize file1 ) --) rz_issue_summarize_file and rz_issue_summarize_file.sh To run these scripts you have to put in the full path to the issue to be summarized. ( e.g. cd $RAZOR_UNIVERSE_DIR/DOMAIN_01/$RAZOR_GROUP/Archive/SCCS $RAZOR_HOME/scripts/rz_issue_summarize_file ./s.I..2-045 ) - In Linux, made RCS the default for new databases, new issues and new versions groups, and new custom issues and versions groups. - Added an "are you sure?" dialog box to the Versions revert function. Razor will now correctly : 1) allow Versions/Threads users to filter files based upon the highest blessing/state attained by the current/latest version of the file (assuming that Versions.filterOnCurrentState, Threads.filterOnCurrentState have been set to True in ~/.Xdefaults and/or ~/.Wdefaults configuration files), 2) allow the Threads users to include/exclude files from selected thread based upon the highest blessing/state attained by the current/latest version of the file (assuming that Threads.filterOnCurrentState has been set to True in ~/.Xdefaults and/or ~/.Wdefaults configuration files) 3) manage project thread updates. *********************************************************** Windows/NT/2000 Release Changes for version 4.3 *********************************************************** - Razor SCC now interfaces with Visual Age. - Razor SCC now interfaces with Visual Basic. - Razor SCC now allows users to choose directory structures. - Razor SCC may now optionally be selected as the default SCC provider during Razor install. - **Note to Razor SCC users..... Microsoft Visual Studio has an option that will prompt the user to retrieve new (i.e. updated) files from the Razor database when a workspace is opened. This option is set by selecting Tools->Options and checking the "Get files when opening the workspace" box on the "Source Control" tab. Users should NOT set this option. When this option is set, the IDE will pull read-only copies of all files in the user's workspace that are in source code control. The IDE does this without determining if any files in the workspace are currently checked-out. Consequently, the user may lose any edits to files in the workspace that are currently checked-out of Razor. When the user invokes Project->Source Control -> Get Latest Version... from within an open project/workspace the IDE considers the check-out status of each file. Consequently, those files currently check-out by the user are NOT overwritten with a read-only version of the file from the Razor DB. **End Note** - Razor ID function now always provides an 8-digit identification. - The Razor Admin tool may now be run by users who have no Admin priviledges. To enable this capability, in windows create a LOCAL group called RAZOR ADMIN. Add a user to that group, that does not have administrative rights. - The update of the permissions file via the Razor Admin GUI has been fixed to correctly show the changes in the GUI. - Windows users may now autolog into Razor using Windows local group login information. To enable local group logins, select the 'Configuration' function from the License Manager pulldown of the Razor Admin tool. *********************************************************** Issue Weaver Release Changes for version 4.3 *********************************************************** Issue Weaver will now: 1. interface better with Linux for display purposes. 2. correctly handle sort filters. *********************************************************** Database Upgrade Instructions for version 4.3 *********************************************************** - For users who are interested in using the new exit.apply function on existing databases, edit the Actions files for Issues, Threads and Versions and add the following line at the end of the table: exit.apply n/a n/a The 'n/a' for the BEFORE script can be replaced with a script of your choice. Note that the AFTER script field is ignored for this function. ********************************************************** Workaround for Known Razor 4.2 Bug ********************************************************** - For some operating systems (AIX is one of them) there is a limitation on the number and length of items in a ONE_OF_MANY, _STACK,_LIST. The limit is dependent on the operating system, the length of each and the number of items. A fix for this will appear in a future version of Razor. In the mean time, the workaround involves putting the stack items in a file, one per line, and referring to the file in the attributes file. The Razor Manual describes the format for file references in Chapter 8 in the ONE_OF_MANY, ONE_OF_MANY_LIST, ONE_OF_MANY_STACK section. ********************************************************** Changes for Version 4.2a.04 ********************************************************** - Incorporate a change in the maximum password length from 8 characters to 16 characters. - Correct editing of Versions attributes. Under certain circumstances, Razor 4.2 produced an error exit when editing attributes in Versions. - Correct function associated with unchecking out files from a command line. Razor 4.2 produces the error message: convert_issue_number () -Invalid string -RZ_STRDUP_WAS_PA Invalid issue number 'RZ_STRDUP_WAS_PA' specified. - Correct connectivity between Linux clients and Unix servers. In Version 4.2, there is a buffer size mismatch between Linux clients and Unix servers and vice versa. This error has prevented mixing Linux and Unix clients and servers. - Correct MAC address identification for NT/2000 servers with multiple network interface cards. Razor 4.2 could not be installed on NT/2000 machines that had multiple interace cards, when the first one encountered returns all zeros. - Correct and improve the Razor SCC product. In Razor 4.2, Razor SCC had some interface problems with some non-Microsoft tools such as Rational Rose. A correction has been made in Razor SCC to improve that interface. Additionally, the 4.2 version of Razor SCC required the presence of some debug-type dll's. SCC Admin has now been rebuilt in release mode and the two required dll's (now non-debug) are provided at install time in the Razor install area. RELEASE CHANGES FOR VERSION 4.2 ** ** -------------------------------------------------------------------------- ** ** ** ** ** ** Refer to Chapter 2 of the manual, "Installing product upgrades", for general upgrade instructions. If upgrading an NT Server installation, refer to Appendix G, "Doing the install". Please refer to the UPGRADE NOTES outlined above for specific instructions. ************************************************************** ****** REMINDERS ****** As you have hopefully noticed, we have changed our domain name. To contact us by e-mail please use one of the following addresses: razor_support@visible.com razor_license@visible.com Check out our web site at www.razor.visible.com. ****** ****** ****** ****** This release DOES NOT include support for HPUX 9.x or Solaris 2.4.x for either Sparc or Intel. Notification was made via Concepts Newsletter 34 (dated June 2, 1999) and Concepts Newsletter 37 (dated October 11, 1999). All users of HPUX 10.x must have a minimum of Razor release 4.1f.02 installed due to HP's implementation of a correction of a Y2K problem. Notification was made via Concepts Newsletter 35 (dated July 12, 1999). ****** ****** ************************************************************** Razor: ===== NOTE=> You are now required to accept the Razor License Agreement when upgrading your installation. NOTE=> The following controls have been added to the Access_list: REMOVE_FOLDER PROJECT_BUMP USER_REPORTS FILE_REPORTS_MODIFY FILE_REPORTS_VIEW ISSUE_REPORTS_MODIFY ISSUE_REPORTS_VIEW THREAD_REPORTS_MODIFY THREAD_REPORTS_VIEW PROJECT_REPORTS_MODIFY PROJECT_REPORTS_VIEW These additions to the Access_list require a manual update to each existing Razor database. Simply add the above controls to the file '$RAZOR_UNIVERSE_DIR/Tables/Access_list'. Refer to $RAZOR_HOME/templates/Tables/Access_list for complete descriptions. This change is not mandatory, however, we strongly recommend updating existing databases so that you can take advantage of the new controls and avoid questions/ concerns in the future. NOTE=> The directory "Report_definitions" will be added to existing databases ($RAZOR_UNIVERSE_DIR) when the database server is started. This area is used by the report generator to store report definitions. Refer to the Razor manual, Chapter 8, "Report Generation". NOTE=> Updated rz_mail_issue_catcher to use the 'next' operation rather than the unsupported 'continue' operation when an error occurs. Users should run rz_install_email_catcher if using the e-mail submission capability to include this update in their database. Enhancements for all users: ========================== A report generator has been integrated with the Razor tool suite. Users may now create and run customized reports on a group and database basis. The report formats include HTML, bar and pie charts. A minimum of version 4.5 of Netscape is required to view these formats. Refer to the Razor manual, Chapter 8, "Report Generation" for details. A Razor tutorial is now available. To install this tutorial run the script 'rz_new_database' and answer "y" (yes) when asked if you would like the DEMO database installed. This initial offering is only available for RCS. NT Server users may install this tutorial via the Razor Admin tool. Decreased memory required to transfer file summary which will increase performance of client/server operations. Distinguish between IRIX and IRIX64 when creating rz_db_exec for new databases. Enhancements for NT Server users: ================================ The Razor Admin Tool has been enhanced to enable complete configuration of your Razor installation. Select "OnApplication" from the "Help" pulldown of Razor Admin for details. Added support for sending e-mail. A default simple MAPI client must be installed. Added installation of the "Razor Inetd" service which is utilized when the license manager is configured to honor the local password file. Enhancements for PC clients: =========================== Added RazorSCC, an interface between Razor and supporting Integrated Development Environment (IDE) applications, to provide the IDE with direct access to existing Razor databases for Razor's file control features. The IDE must support the Microsoft Source Code Control (SCC) API specification. RazorSCC can be installed as part of a RazorNT or RazorPC install procedure, and must be installed on each PC that will use it. Issues: ====== Corrected introduction of issues via e-mail to first check for site specific script ($RAZOR_UNIVERSE_DIR/Scripts). Updated documentation to note that when formatting date/time for the TIME_STAMP attribute conversion characters must include delimiters. Versions: ======== Corrected merge failure which occurred when only line 1 of two files differed. The introduce and check-in dialogs now honor the CHECKOUT access control. Corrected problem that occurred when the OK button on the revert dialog was double-clicked. Will not show files and directories in the introduce list that are not writeable. Where appropriate, the folder name will be indicated in the Introduce dialog title. File modifications may now be filtered by time as well as date. The PROMOTE entry in the Access_list will control the availability of the Promote functionality ONLY IF the file 'Promoters' does not exist. Corrected an intermittent problem whereby the "Directory" text field of the various Versions dialog would not reflect the directory chosen by the file/directory chooser. Corrected problem where the database server was exiting upon rename of folders. Corrected problem when associating issues to actions and the issues group name exceeded 32 characters. Threads: ======= Deleting a file and introducing a file of the same name will no longer confuse threads which referenced the file. Corrected problem with Project thread extraction scripts applied to an NT hosted database. Changed handling of folder selection during Thread editing with the Include/Exclude dialog displayed to prevent inadvertent file selection in the thread. UNIX Remote Clients: =================== Corrected problem with RAZOR_EDITOR. Added logic to detect multiple IP addresses. Resolved problem with DISPLAY environment setting. Command Line Interface (razor): ============================== Erroneous disconnect error message when promoting an issue via the command line has been eliminated. Updated promote_issue to allow the modification request to complete before invoking the after script. Updated to accept an unlimited number of related issues. The AFTER script for removals will be executed for all successfully removed files and folders. Razor PC clients: ================ Corrected a problem in versions that was evident when operating in certain time zones. Made the database login dialog resizable so the database history list is no longer partially obscured. IssueWeaver: =========== NOTE=> IssueWeaver is NOT compatible with Microsoft's Internet Information Server (IIS). Corrected setting of century in IssueWeaver info script (rz_iw_info). Corrected problem when an after script uses the command line interface and is executed via IssueWeaver. Scripts: (Razor_/examples) ======= The script 'update_state_dates' has been corrected to properly update 2-digit years to 4-digit years for both the 20th and 21st centuries. Examples: (Razor_/examples) ======== Added example script which will report on the number of open and closed issues for specified time period. Corrected mail_issue_changes to handle non-default issues groups. Corrected example script mail_from_attrs. The example script list_open_issues will now output the string NONE in the open issue section if none are found. Corrected whats_checked_out and whats_checked_out_html to ignore issue and thread groups. Corrected Attributes file for customized issue groups to allow the example script 'build_default_permissions' to correctly create the Permissions file. -------------------------------------------------------------------------- ** ** ** v.4.1(g).05 ** ** ** Issues: ====== Corrected problem with global database synchronization. Threads: ======= Corrected the thread extraction script to handle filenames that contain a "$". Versions/PC: =========== Corrected a problem that occurred during file introductions from a Novell drive. Command Line Interface: ====================== Corrected file control interfaces to handle filenames that contain a "$". ------------------------------------------------------------------------ ** ** ** v4.1(g).04 ** ** ** Razor License Manager: ===================== Corrected problem on some Linux platforms that allowed multiple license managers to execute. -------------------------------------------------------------------------- ** ** ** v4.1(g).03 ** ** ** Razor: ===== Eliminated redundant open file descriptors to alleviate resource constraints. Corrected database server crash when kid_of_threads is explicitly "killed" by a user. Issues: ====== E-mail submission/modification will correctly indicate a failure if the database is not running. This correction affects both global database synchronization and e-mail submission. Threads: ======= Modified command line editing of project threads to handle long thread names. Razor Admin Tool: ================ Corrected failure to start tool on some PC's. Razor PC: ======== Corrected pagination of printed output. Cleaned up temporary files left by client applications (issues, versions and threads). -------------------------------------------------------------------------- ** ** ** v4.1(g).02 ** ** ** Razor NT/IssueWeaver: ==================== Corrected problem seen with version 1.3.9 of the Apache web server on NT. Razor installations on NT using IssueWeaver and version 1.3.9 or greater of Apache should upgrade BOTH the Razor installation and the IssueWeaver installation (refer to the IssueWeaver manual, Chapter 2, "Step one: check your environment", the subsection "Special instructions when installing on Windows NT"). --------------------------------------------------------------------------- ** ** ** v4.1(g).01 ** ** ** Razor: ===== Fixed a problem which caused the database server to hang on startup when running against a file group without file id settings. --------------------------------------------------------------------------- ** ** ** v4.1(g) ** ** ** Razor: ====== NOTE=> Added support for IRIX 6.5 (64-bit) OS. NOTE=> Printing within issues has been changed to support local printing. This change affects printing of specific issues as well as printing reports. The display output of reports run within issues now includes a "Print" button. Selecting this button will print the report to the printer defined via "Print Setup". PC users may use the standard Print dialog to control the print destination. To comply with this new printing scheme, upgrade existing installations as follows: o Customized report scripts should be modified to reference RAZOR_LPR rather than _LPR_ for printing. o Each user should set their print command via the "Print Setup" dialog by selecting the "Print Setup... " item of the issues "File" pulldown menu. Since some of the Razor supplied report scripts printed directly, automatic printing is now supported via the file 'Reports'. Refer to Chapter 9 of the manual, "Auto-printing of report script output". The new print scheme effectively obsoletes the old method of print customization which involved the _LPR_ macro and files $RAZOR_UNIVERSE_DIR/rz_print_opt and $HOME/.rz_print_opt for printing from the issues client and IssueWeaver. Although _LPR_ has been replaced by RAZOR_LPR, it is still available and may be used with custom scripts. Since issue report scripts defer printing to the requesting client, report output generated from within IssueWeaver may be printed by using the browser supplied print function. NOTE=> The script 'rz_issue_tally" has been modified to only accept the following two methods of invocation: rz_issue_tally rz_issue_tally , where contains a list of issues. A third method which accepted a comma-separated list of issues has been obsoleted. Custom scripts which reference this obsolete method should be modified. Enhancements: The Razor Admin tool is now available for Windows NT. This tool is an easy user interface for installing license keys, starting/stopping the license manager, creating databases, etc. Many of the administrative functions that could only be performed via command line scripts (still available) can now be handled via this GUI. Refer to Appendix G of the manual, "Starting Razor admin" . Tailored issue and file control groups may now be added to existing databases via the Razor Admin tool (NT Server only) and the script 'rz_add_custom_group'. Refer to Chapter 2 of the manual, "Making additional custom groups". The size of remote login panels may now be modified via an Xresource (see Razor_/examples/Xdefaults.sample). Corrections: The umask will be honored when files are extracted from the database (via checkout or thread scripts). Added logic to test for binary incompatability between SunOS and Solaris. Updated Role processing to correctly honor roles with multiple group definitions. Corrected problem on Linux platforms which caused the kid_of_* processes to run continually rather than sleep while not in use. Updated commentary in templates/Tables/Access_list to more accurately define user and group. Issues: ======= Temporary preload files will now be properly removed. The TEXT_PANE attribute label should be used to include a title for the two separate text areas on an issue form (prior to 4.1(d) this functionality was only available via the Problem and Solution template files). Issues/PC: ========= Corrected problem with the PC issues client which resulted in duplicate filters. Versions: ======== Corrected problem introduced in 4.1f.03 which caused the versions tool to exit when attempting to merge. Corrected problem which potentially caused issues to appear twice in the issue list on the versions check-in panel. Prohibit introduction of files whose name contains a single quote. Corrected a potential problem branching files with RCS as the archive engine. Problem would occur if TMP, TEMP or TMPDIR had been overriden to a non-writeable directory. Corrected problem associated with promoting multiple files in rapid succession. Corrected filename passed to after scripts for checkin, checkout and uncheckout when a branched file is involved. Versions/PC: =========== Corrected problem with the Versions/PC client where the diff window would not remain in the foreground after the diff completed. Threads: ======= Corrected problem of multiple occurrences of the same thread/group being allowed in a project. NT Server: ========= The Access list for NT server no longer requires the inclusion of hostname for the following controls: ADD_USER, MODIFY_USER, REMOVE_USER, RAZOR_DOWN and RAZOR_LM_DOWN. New NT Server installations will be provided with Razor identification information via Notepad. Command Line Interface: ======================= The name of the unchanged file that was not checked in either because the option FileCheckIn is set to MustChange or FileCheckIn is set to WarnIfNoChange and the user has declined to checkin the file will be displayed following completion of the command. Corrected "razor who" to include IssueWeaver connections. Added informative error message when "razor new_issue" fails because the user has no issues client subscribed to the required group. Scripts: (Razor_/scripts) ======== Corrected rz_compare_thread to handle spaces in file names and directory paths. Corrected rz_rename_attr, rz_rename_attr and rz_remove_attr to accept case insensitive responses. Modified razor_learn and razor_learn_file functions from rz_toolbox to remove ALL commas that separate values. Added support for the file specification for ONE_OF_MANY and X_OF_MANY attributes to rz_rename_attr_val and rz_remove_attr_val. Modified rz_remove_attr, rz_rename_attr, rz_rename_attr_val to better handle large lists of files/issues. Corrected the razor_learn function in rz_toolbox to handle filenames that include "@". Examples: (Razor_/examples) ======== Corrected the example script thread_to_latest to ignore branches when updating a thread to the latest version. The following resources are now honored by PC clients (refer to Wdefaults.sample): Threads*SelectionsPulldown.SelectOne.set Threads*SelectionsPulldown.SelectAny.set Threads*SelectionsPulldown.SelectOne.sensitive Threads*SelectionsPulldown.SelectAny.sensitive IssueWeaver: ============ The label for the first TEXT_PANE will now be properly formatted. Labels, as viewed via IssueWeaver, are now right justified, consistent with the issues GUI. The LABEL attribute value is left justified with the label field. Updated button descriptions to reflect usage rather than image displayed. Supports the RAZOR_ISSUE_NUMBER meta tag, consistent with other RAZOR_ISSUE_xxx meta tags and the documentation. Fixed a problem where, under certain circumstances, not all meta tags on a line would be replaced. X_OF_MANY_LIST and ONE_OF_MANY_LIST attributes will be properly displayed when set to readonly via the rules file. ** RELEASE CHANGES ** ** ** -------------------------------------------------------------------------- ** ** ** v4.1(f).03 ** ** ** Razor: ====== Corrections: Modified Mapping file processing for deleted files to prevent extraction problems the first time the server recreates this file. Versions: ======== Corrected handling of binary file whose name contains shell characters such as "$". Scripts: (Razor_/scripts) ======== Corrected the razor_folders command to properly output only folders. Examples: (Razor_/examples) ======== Corrected syntax in create_version_doc. IssueWeaver Admin Tool: ====================== Since web server's do not universally set the environment variable, DOCUMENT_ROOT, the script 'rz_iw_admin' installed in the web server's cgi-bin will set and export DOCUMENT_ROOT as well as invoking the IssueWeaver Admin Tool script in $RAZOR_HOME. This script will be created during the installation of IssueWeaver (execute 'rz_iw_install') for both new installations and upgrades. -------------------------------------------------------------------------- ** ** ** v4.1(f).02 ** ** ** Razor: ====== NOTE=> Two HPUX executables are now available. The default executable supports HPUX 10.x and higher and is Y2K compliant. Until December, 1999, an HPUX_9.x executable will also be available. Corrected usage statement for command line interface "add_user" in README.RazorNT. IssueWeaver: ============ Corrected problem with installation of IssueWeaver on NT. -------------------------------------------------------------------------- ** ** ** v4.1(f).01 ** ** ** Refer to Chapter 2 of the manual, "Installing product upgrades", for general upgrade instructions. Please refer to the UPGRADE NOTES outlined above for specific instructions. Razor - General: ================ NOTE=> Sites that prefer to use both UNIX logins and the Razor password file for remote user validation may do so by invoking the Razor license manager (razor_lm) with the "-P" option. You can force this option regardless of how the razor_lm is invoked by a setting in the file $RAZOR_LICENSE_DIR/License.conf. A template for this file may be found in $RAZOR_HOME/templates. This file will be added to the Razor_lm directory ($RAZOR_LICENSE_DIR) for new installations. Changes to $RAZOR_LICENSE_DIR/License.conf will be honored when the license manager is restarted. Refer to Chapter 2, "License manager", of the manual for details. NOTE=> When requesting license keys, please forward the entire output of the command "razor id" to 'license@tower.com'. Corrections: Handle condition in razor command line application where RAZOR_UNIVERSE_DIR is not set when invoking "razor up" and "razor down". Corrected database synchronization problem which would occur if the version of a given issue is more than one version out of sync between the master and slave sites. Corrected problem affecting database synchronization where slave updates would occur before master updates when submitted at slave site for non-default issues groups. Improved database server error handling to deal with slow and/or poorly configured network connections. Corrected problem encountered during archival operations when moving a file on Linux using Redhat 6.0. NT Server: ========= Corrected problem installing a database to the root directory of a drive. Corrected problem with checkin of files with Razor installed in other than the installer provided default location. Corrected problem with script attr_to_xy when an output file was not provided on the command line. Versions: ======== The AFTER script readonly.apply now sets the version number to the selected version rather than the latest version of the file. Added processing to the rename functionality to remove multiple "/" from the new name prior to update of the database. Versions/PC: =========== Corrected problem checking out files to network neighborhood. Threads: ======== Corrected problems extracting files within folders containing embedded spaces. Corrected problem extracting projects which contain threads whose name length is greater than 40 characters. To repair existing projects that include such threads simply resave the project after deleting and readding the thread. Take care to specify the correct thread version. Corrected problem with thread extraction which occurred with threads which included files that have been renamed. IssueWeaver: ============ NOTE=> Upgrading your current installation of IssueWeaver by invoking the script 'rz_iw_install' will no longer create a "new" Razor_iw_lib. New files will be added to the current Razor_iw_lib. To force the creation of a "new" Razor_iw_lib, the "-o" parameter is honored by 'rz_iw_install'. The file 'rz_iw_site' located in your web server's cgi-bin directory may be used to add site specific information to the IssueWeaver executable. An example of usage, would be to export the time zone setting in 'rz_iw_site'. IssueWeaver Admin Tool: ====================== Corrected potential error from nawk. Examples: (Razor_/examples) ======== Updated example script issue_closed_since to support an issue group specification and century value in input date. -------------------------------------------------------------------------- ** ** ** v4.1(f) ** ** ** Razor - General: ================ NOTE=> Sites that prefer to use UNIX logins rather than the Razor password file to validate remote user and IssueWeaver logins may do so by invoking the Razor license manager (razor_lm) with the "-p" option. You can force this option to be used regardless of how the razor_lm is invoked by a setting in the (NEW) file $RAZOR_LICENSE_DIR/License.conf. A template for this file may be found in $RAZOR_HOME/templates. This file will be added to the Razor_lm directory ($RAZOR_LICENSE_DIR) for new installations. Changes to $RAZOR_LICENSE_DIR/ License.conf will be honored when the license manager is restarted. The Change Password selection on the remote login panel will be insensitive when the local password file is being used. Enhancements: Added time stamp output to debug and error outputs. Expanded limit of X_OF_MANY and ONE_OF_MANY attributes to 1024 items. Corrections: Service expiration date is now correctly displayed when "razor license_info" is run. NT Server: ========= Corrections: Corrected problem which occurred if TMPDIR was defined as a System environment variable using the WIN32 directory style instead of POSIX. Issues: ======= NOTE=> The directory "Latest" must exist for all issues groups. If this directory does not exit, take the database server down and, as the owner of the database, create the "missing" directory: $RAZOR_UNIVERSE_DIR/DOMAIN_01/++ISSUES++./Latest Restart the database server. As the owner of the database run the following script for each issues group that was "missing" the "Latest" directory: $RAZOR_HOME/scripts/rz_issue_build_latest Corrections: Corrected printing of issues in databases with attributes labeled "Version" and/or "Issue". Versions/PC: =========== Corrected problem on WIN95 checking files out to root drive. The following resources are now supported by Wdefaults: OrigInfo.set (refer to the check-in panel) Binary.set (refer to the introduce panel) Auto-detect.set " Threads/PC: ========== Corrected problem of the "text mode" tool property not always being honored during thread extractions. Scripts: (Razor_/scripts) ======== For new databases, the setting of path has been corrected to remove the prepending of colons upon multiple instantiations of rz_prep.sh. The example "smart" rz_prep files have also been corrected. Corrected minor bug in function razor_learn of rz_toolbox. Corrected the functions razor_files & razor_folders in rz_toolbox to check for empty directories. Examples: (Razor_/examples) ======== Group may now be passed to is_member_of_role. RAZOR_USER, if defined, or USER will be verified as a member of the input role. Corrected minor problem in summarize files and whats_checked_out. -------------------------------------------------------------------------- ** ** ** v4.1(e) ** ** ** Razor - General: ================ NOTE=> Users accessing Razor databases via remote client applications (including PC client, UNIX remote client and/or IssueWeaver) are no longer required to have UNIX accounts. A "guest" login will be honored for world access to the database prior to the creation of a Razor defined password file. For IssueWeaver, the "guest" login will be honored even if the rule VERIFY_PASSWORD is "YES". [Chapt. 2, "Remote client password"] NOTE=> We strongly suggest that the Razor administrator create a password file for remote users as soon as possible after completing the upgrade. The command line interface, "razor add_user", must be used to create/modify the Razor password file. [Chapt. 2, "Remote client password"] NOTE=> The file '$RAZOR_LICENSE_DIR/Databases' must contain full pathnames. NOTE: The paths to databases must match the information displayed when the user enters the command, "razor info". [Chapt. 3 "Switching between databases & issues groups"] NOTE=> RazorNT installs as "Razor". Pre-4.1e Razor PC clients installed as "Razor". If you currently have a Razor installation on the PC where you will be installing RazorNT, you must FIRST uninstall the Razor PC client. Starting with this release, the Razor PC client will be installed as "RazorPC". Refer to README.RazorNT for installation instructions. New functionality: The following have been added to the command line interface to support the Razor password file: [Chapt. 6, "Password functions] razor add_user razor modify_user razor remove_user razor user_info razor passwd razor passwd_info The following access controls have been added (refer to Razor_/templates/Tables/Access_list): [Chapt. 8, "Access controls"] ADD_USER, MODIFY_USER, REMOVE_USER* modify Razor password file RAZOR_LM_DOWN "stop" Razor license manager USER_SCRIPTS* control ability to create/modify scripts via versions GUI *New databases will be created with this functionality disabled. A total Windows NT environment is now supported. The license manager and database server(s), as well as the previously supported clients, will now execute on the Windows NT platform. Please contact 'sales@tower.com' for pricing. Enhancements: Remote clients now maintain tool properties and filters locally. [Appendix B, "Personal files"] Added the ability to include attribute settings for ONE_OF_MANY* and X_OF_MANY* by using the file: tag where is the name of a file in the Tables directory. The format of this file is any combination of comma, space, newline delimited entries. [Chapt. 8, "Attribute types defined"] Enhanced database server to avoid problems with license manager connection during long startup times. Made database server more tolerant of communication errors. Added mechanism to deal with unwriteable temp directories. Added some Web-related file-type glyphs (Java, HTML, and SHTML). Corrections: Corrected mishandling of hosts with embedded spaces in the hostname. Corrected documenation regarding the environment variable RAZOR_FILE_LIST with reference to commands capability. [App. B, "Commands"] Issues: ======= NOTE=> The required text field that is used as a "title" on the main issues list must contain a minimum of one non-space character. This requirement corrects an archive engine generated error. [Chapt. 3, "Rules and restrictions"] NOTE=> When using the TIME_STAMP attribute, please note that not all descriptors for ctime are supported. In particular, the descriptor "%e" is not handled on SunOS, HPUX and Linux. We suggest the use of "%d". [Chapt. 8, "Attribute types defined"] Corrections: FindText dialog now behaves correctly when the Regex toggle is selected. Corrected problem caused when a TEXT_PANE attribute is defined BEFORE a STATE attribute. Versions: ========= Enhancement: Resizing the browse selection dialog will expand the main list. Added a warning notice to the user when attempting to promote a file to its current state/version. Added processing to better deal with bad USER_UTIL entries in the .razorrc file. [App. B, "Personal files"] Correction: Added the use of the -w flag for RCS ci operations so that the proper Author will be set. Corrected problem of occasionally not being able to checkin binary files. Corrected problem introducing "large" files on SCO Directory structures will be created after all "before" scripts are executed during checkout operations. Keyword expansion will now be properly honored upon checkout for edit from an RCS file group. Modified rz_server to better handle very long paths in database hierarchy when checking a file out/in and issues have been related to the operation. Versions/PC: ============ Corrections: Corrected problem of erroneous data appearing on the initial use of the diff dialog. Threads: ======== NOTE=> Changed the default behavior for including branches in threads. Only one version of a file (when a file has branches) can be included in a thread. Selection of files for a thread (Blanket Selection, or Include based on Issues) will select the greatest version of a file from the selection list or filter. The previous behavior of Razor (allowing a trunk and branches or multiple branches to be included) may be selected from the Edit Thread Selections pulldown or via Xdefaults. [Chapt. 5, "Trunks vs. branches"] Enhancements: To better explain the purpose, the label "State:" has been changed to "File states:" on the "Related Issue List" dialog. [Chapt. 5, "Defining threads by related issues"] If nothing is entered in the Comment field of the Save dialog, the user will be reminded to enter a comment rather than a title. [Chapt. 5, "Saving it back to the database"] Revert operations will be included when the Check-in toggle is selected on the "Related Issue List" dialog. [Chapt. 5, "Defining threads by related issues"] Corrections: Corrected problem with thread compare when similar folder names include special characters. Corrected threads bug which occurred on AIX and OSF when attempting to create a thread for an empty file group. When threads create.apply before script fails, the application will no longer be confused when attempting to reference information about selected files. Command Line Interface: ======================= New functionality: Information about number of licenses and expiration dates is now provided via the command "razor license_info". [Chapt. 6, "Modifying/reviewing the license information"] Added command line interface to bring the Razor license manager down, "razor lm_down". [Chapt. 6, "Starting and stopping the license manager"] Added functionality to rename a file or folder: razor -c rename -f -g -n [Chapt. 6, "Renaming a file or folder"] Added a new commandline parameter, "-m" for the commands, "modify" and "new_thread", to allow multiple versions of a file (trunk and branches) to be included in a thread. [Chapt. 6, "Working with threads"] Corrections: Updated the help description. Honor non-default issues groups during command line uncheckout operation. Scripts: (Razor_/scripts) ======== The script rz_add_users will convert a file in the specified format to Razor remote password entries. [Chapt. 2, "Batch entry of passwords"] Updated rz_install and rz_new_database to better utilize existing installation information and to correct some minor deficiences. Enhanced rz_toolbox to handle attributes with dots and/or dashes in attribute values or names. Corrected rz_compare_threads to continue compare after a difference is found. Examples: (Razor_/examples) ======== Added razor_browse.emacs that starts up Emacs for file browse. Corrected typo in state_rate in reference to RAZOR_GROUP. Corrected thread_to_latest to correctly handle output of razor_files -o. Updated notify_assigned to use rz_utils. Updated Xdefaults.sample to reference the resource setting for groupColumns for issues and threads. Updated promote_files_in_thread to honor the latest version of the thread if no version is specified at invocation. Updated parsing of project files in create_version_doc. IssueWeaver: ============ NOTE=> The file 'Razor_iw_lib/IW_valid_users' has been superseded by the Razor password file. The entries in 'IW_valid_users' may be easily added to the password file via the script Razor_/scripts/rz_add_users. [Razor Manual, Chapt. 2, "Batch entry of passwords"] New functionality: The "latest" addition to the Razor tool suite is the IssueWeaver Admin tool. This tool provides an easy mechanism for creating style definitions which may be used to customize the "look" of the various issues groups associated with your Razor databases. [IssueWeaver Manual, Chapt. 5, "Customizing styles - the Admin Tool"] To support the Admin Tool, the directory Razor_iw will be created in the web server's documents directory during installation. The file 'Razor_iw/users' may be used to control access to the Admin tool. The file 'Razor_iw/databases' is used to populate the RAZOR_UNIVERSE environment of the Admin tool. [IssueWeaver Manual, App. B, "Administration files"] Enhancements: Body templates may now reference attributes via the following META tags: [IssueWeaver Manual, Chapt. 4, "Attribute-defined"] RAZOR_ATTR_FIELD_ RAZOR_ATTR_LABEL_ RAZOR_ATTR_VALUE_ By default, if both VERIFY_USER and VERIFY_PASSWORD are set to NO, the issue list will be displayed. To force the login page to be displayed, set the rule FORCE_LOGIN to YES. Users may login without providing a user name (default is "nobody"). The default user name may be modified via the rule, DEFAULT_USER. [IssueWeaver Manual, App. B, "Rules file"] The functionalify of the file 'Razor_iw_lib/IW_invalid_users' has been replaced with the Razor password file. This file may be used to deny access via IssueWeaver to users listed in the password file. The background color for the blocks style has been changed from black to light blue. Corrections: Corrected problem where a user was unable to create a new issue when the access control ISSUE_CREATE was enabled for this user but ISSUE_VIEW and/or ISSUE_MODIFY was disabled. [Razor Manual, Chapt. 8, "Access controls"] Removed duplicate entry of "nobody" from IW_invalid_users file. -------------------------------------------------------------------------- ** ** ** v4.1(d) - Patch 06 ** ** ** Issues: ====== Corrected $RAZOR_HOME/examples/Xdefaults.sample to correctly reference the two text panes on an issues form. These areas are now referred to as Text1 (formerly ProblemText) and Text2 (formerly SolutionText). The file $RAZOR_UNIVERSE_DIR/Xdefaults should be updated to correctly reference these text areas for existing databases that are using these resource settings. The height of the scrolling text areas are now controlled by the following X resources: Issues.IssueForm*TextForm1.height: 100 Issues.IssueForm*TextForm2.height: 100 The addition of these resource settings corrects a problem observed when running on Solaris 2.6, HPUX 10.x and SCO. Corrected problem where font setting was reset to default when switching between databases. Command Line Interface: ====================== Corrected handling of before action script error exits for the functions new_folder, new_thread and modify (thread and project). Modified remove_folder to run ALL before scripts prior to removing any files/folders. If any before script fails, the operation will be terminated and no files/ folders will be removed. IssueWeaver: =========== TIME_STAMP attributes which include the preload and non- writable options will now be properly recorded in the database for new issues. -------------------------------------------------------------------------- ** ** ** v4.1(d) - Patch 05 ** ** ** Razor - General: =============== Enhanced processing so that RCS users using $Log$ will see the proper username rather than RAZORDB. Removed unnecessary file compression during file checkin. If using the alternate compress capability, the flag -fc is now passed to the script. The script MUST return 0 on success or 2 if the compress worked but made the file bigger. All output MUST go to stdout. (NOTE: Users may choose an alternate compress capability by creating the script $RAZOR_UNIVERSE_DIR/Scripts/compress.) Threads: ======= Corrected problem of History file not being properly updated when a thread is created including files based on related issues. -------------------------------------------------------------------------- ** ** ** v4.1(d) - Patch 04 ** ** ** Issues: ====== The last line of the first text area will no longer be entered as the first line of the second text area. Command Line Interface: ====================== Corrected problem with issue promote when a before script is attached. -------------------------------------------------------------------------- ** ** ** v4.1(d) - Patch 03 ** ** ** Razor - General: =============== Added processing to handle RAZOR_TMP being removed when database server is running. Threads: ======= Included MERGE-CHECK-IN as a "Check-in" action as it relates to the "Related Issue List" dialog (updating a thread based on issues). -------------------------------------------------------------------------- ** ** ** v4.1(d) - Patch 02 ** ** ** Razor - General: =============== Add README.Upgrade to the release distribution highlighting instructions for upgrading pre-4.1d databases to 4.1d and beyond. Note that these instructions may be found in this document, in the section entitled "IF UPGRADING TO 4.1d". Issues: ====== Corrected problem induced when reset was applied on an issue form. Corrected potential failure when selecting an issue via the "Which Issue?" dialog. Versions: ======== Correctly identify the versions of a file which contribute to a merge checkin of that file. -------------------------------------------------------------------------- ** ** ** v4.1(d) - Patch 01 ** ** ** NOTE=> Users should make sure that the FileCheckIn option contains a TAB separated field rather than a SPACE separated field in $RAZOR_UNIVERSE_DIR/Tables/Options (if it exists). For databases created prior to 4.1d, users should also update $RAZOR_UNIVERSE_DIR//Tables/Options and $RAZOR_ UNIVERSE_DIR/templates/Versions_tables_templates/Options. Razor - General: ================ Enhanced processing of user roles to work properly with IssueWeaver. PC client applications: ======================= Corrected problem for remote clients being unable to connect when the IP address contained a zero. -------------------------------------------------------------------------- ** ** ** v4.1(d) ** ** ** Razor - General: ================ NOTE=> The Razor database server will now inherit the search path of the user that starts it. All users who will be starting the Razor database server(s) must have the location of general purpose UNIX utilities (i.e. "cp") on their search path. If Razor is started automatically at boot time, the database server(s) will inherit "root's" search path. We urge you and your System Administrator to review the start-up script currently being used. NOTE=> If RCS is selected as the archive engine for any group within a database, all users (including root) who start the database server must include RCS on their search path. NOTE=> Extensive changes have been made to the scripts rz_vcs.sccs and rz_vcs.rcs. If you have customized these scripts and you need to retain your implementation, make a copy of the current rz_vcs script (rename to rz_vcs.orig) then copy the "new" script(s) from $RAZOR_HOME/scripts to $RAZOR_UNIVERSE_DIR/Scripts and add your customization. Remember to name the "new" script 'rz_vcs' and make sure that is has execute permission (chmod a+x rz_vcs). NOTE=> Local copies of rz_mail_catcher found in each subscribed user's home directory, $HOME/.rz_mail_catcher have been obsoleted. NOTE=> Example scripts have been updated to reflect changes relating to the archival system. If you have attached scripts to your existing databases, we suggest that you review the changes to $RAZOR_HOME/examples. Some changes may need to be incorporated in your existing scripts. Also review $RAZOR_HOME/examples/ README for additional example scripts including generation of a software version document. NOTE=> Removed the configuration file $RAZOR_UNIVERSE_DIR/Admin. Controlling who can bring the database server down is now handled by the Access_list file. Users who are currently controlling access to the database server via 'Admin' must use the new file 'Access_list'. A template may be found in $RAZOR_HOME/templates/Tables. NOTE=> Customized user scripts that are attached to Razor actions and are expecting output via "Razor_notice" should be changed to reference "${RAZOR_TMP}/Razor_notice.${RAZOR_PID}.${ERR}" rather than "/tmp/Razor_notice.$RAZOR_PID.$ERR". NOTE=> The default issues group (++ISSUES++) is no longer required. Users may remove this group (with the database server down) as long as the database contains at least one issues group. NOTE: IssueWeaver users should make sure that there are no rules files that reference this default issues group after it is removed. ======================= ======================= New functionality: The ability to merge two versions of a file has now been added to versions. Select a file (non-binary) on the main versions display and choose Merge on the Utilities pulldown menu. UNIX remote client application now supported. Refer to the manual for installation instructions. Use the following commands to invoke the tools remotely: issues -remote & versions -remote & threads -remote & The necessary files required for a UNIX remote client installation are a subset of the files included in a Razor installation. We have provided a script that will create a compressed tar file for a remote client installation. Please refer to: Razor_/scripts/rz_create_remote_distribution. Added capability to use RCS as the archival engine for issues and threads. When creating a new database (rz_new_database) and/or creating a new group (rz_add_group or rz_add_issues_group), users will be prompted for which archival engine to use. Please note that you may choose different archival engines for each group within a database. Added a mechanism to configure control of specific operations on a role/group/user basis. The file 'Access_list' defines the operations which may be configured for control. This file may exist at the universe level ($RAZOR_UNIVERSE_DIR/Tables) or at the group level ($RAZOR_UNIVERSE_DIR/DOMAIN_01/ /Tables). Group settings override universe level settings. The file '$RAZOR_UNIVERSE_DIR/Tables/Access_list' will be created for all new databases. To add this functionality to existing databases, copy $RAZOR_HOME/templates/Tables/Access_list to the universe and/or group level Tables directory. To support configurable control of specific operations via the file 'Access_list', the following RAZOR_ACTIONS have been renamed: threads/projects: SAVE_BEFORE THREAD_MODIFY_BEFORE SAVE_AFTER THREAD_MODIFY_AFTER PROJECT_MODIFY_BEFORE PROJECT_MODIFY_AFTER issues: CREATE_BEFORE ISSUE_CREATE_BEFORE CREATE_AFTER ISSUE_CREATE_AFTER MODIFY_BEFORE ISSUE_MODIFY_BEFORE MODIFY_AFTER ISSUE_MODIFY_AFTER Please review customized scripts and make the appropriate substitutions where necessary. Several additions have been made to the Actions template for both versions and threads. Refer to $RAZOR_HOME/ templates/Versions_tables_templates/Actions and Threads_tables_templates/Actions. These template files may be copied to the templates directory in any existing Razor database. If you would like to take advantage of these new actions in existing file control groups, please copy the new Actions template file to the appropriate database group Tables directory: $RAZOR_UNIVERSE_DIR/DOMAIN_01//Tables/ $RAZOR_UNIVERSE_DIR/DOMAIN_01/##Threads/Tables We suggest that you copy the existing Actions file before getting the new template (i.e. "mv Actions Actions.orig"). Please note that previous action names are still supported for existing Actions files. For databases created with 4.1d, the definition scripts rz_prep & rz_prep.sh may be invoked multiple times without enlarging the path variable with multiple instances of the RAZOR path. To add this functionality to existing databases, refer to $RAZOR_HOME/examples/rz_prep.smart (and rz_prep.sh.smart). Added new X_OF_MANY_LIST and ONE_OF_MANY_LIST attributes. Their function is identical to that of X_OF_MANY and ONE_OF_MANY, respectively. The only discernable difference is how these attributes are presented via the Razor graphical user interface. New option for separate text areas allows the Razor administrator to independently control access (Writeable, Readonly or AppendOnly). Added new attribute TEXT_PANE. This attribute is used to label the two free-form text areas at the bottom of an issue form. The definition for TEXT_PANE in the Attributes file must include a unique name (Column 2) of the format TEXTn where n is either 1 or 2 representing the first or second text area. Column 3 is the label string which will be placed at the top of the defined text area. When renaming a TEXT_PANE attribute VALUE (via rz_rename_attr_val), the old value is inconsequential; the attribute value will be renamed to the new value regardless of what the user enters for the old value. The rz_rename_attr_val script takes the following as args . The script rz_mail_issue_catcher may be modified to disable automatic success notification. Added GUI-based application, rz_notice, similar to Xmessage which accepts query of user input without invoking an Xterm session. Added Commands functionality for versions and threads. Added resources for both versions and threads diff dialogs: Versions.Diff*DiffText.columns: 180 Versions.Diff*DiffText.rows: 40 Threads*DiffText.columns: 100 Threads*DiffText.rows: 15 Enhancements: Added capability to detect and handle variations in machine time between the database server and client applications. Improved error message when a referenced file cannot be found during Bitmap processing. Made pulldown menu items consistent throughout all tools (issues, versions and threads). Corrections: Modified e-mail catcher scripts to use RAZOR_GROUP rather than GROUP. Spaces in filenames are handled for rename and remove functions; "diff'ing" of an archived file with a file outside of Razor; scripts (both in $RAZOR_HOME/scripts and $RAZOR_HOME/examples). Corrected the script rz_remove_attr_val to handle removal of the first state. The scripts to rename/remove attributes and/or their values (rz_rename_attr, rz_rename_attr_val, rz_remove_attr, rz_remove_attr_val) will now update the Attributes file even if no files exist in the group. Users who update attributes on existing databases via rz_remove_attr and rz_rename_attr will be reminded to update the IssueWeaver rules files. If an attribute value is removed from a ONE_OF_MANY, ONE_OF_MANY_STACK or ONE_OF_MANY_LIST via the script rz_remove_attr_val, Info files that currently reference the removed attribute value will be changed to reference the first defined value. Insensitive file will be updated when the script to adjust attributes is executed (i.e. rz_rename_attr, rz_rename_attr_val). Corrected a problem that occasionally occurred when attempting to connect to the server. The error message would be "There seems to be a problem using the defined ports to connect to the database server." Correct lock-up condition which occurred when using in combination with a continue notice. Corrected overwriting of License_status file. Removed memory leak caused when rebuilding a Mapping file that references deleted files. Modified the Help dialog processing to prevent infinite number of help dialogs. PC client applications: ======================= The following command line options are supported by the client applications: [-universe ] [-rc ] [-group ] [-debug] The error log window may now be dismissed. Now supports a disconnect/reconnect capability. Added capability to specify which IP address is the one by which the PC client machine is known to the network on which the database server host resides. This applies in cases where a PC has multiple IP addresses. Classically, one is a LAN IP and the other is a PPP connection. The resource AbsolutePath.set is now honored by Wdefaults. Enhanced Help information on the Razor Desktop for Windows client application. License Manager: ================ Eliminated defunct processes created by license manager on DEC OSF. Corrected OS specific problems encountered when executing "razor info" when a license manager is not executing. Issues: ======= New functionality: When creating or modifying issues, the values on the issue form will be dumped to the user's environment as variables in the form: RAZOR_ATTR_ For STATE attributes, each state value will be represented as: RAZOR_STATE_ The current state will be: RAZOR_ATTR_ The name of the object will be: RAZOR_NAME The information which appears in the Info file will also be available in RAZOR_LATEST_VERSION, RAZOR_LAST_MODIFIED, RAZOR_LAST_MODIFIED_INT, RAZOR_NUM_STATES, RAZOR_TIME_CHECKED_IN, RAZOR_TIME_CHECKED_IN_INT. A new option has been added to the Reports file. If the third field is "env", the report script will be invoked once for each selected item (just as it is when nothing appears in field 3). Instead of extracting a copy of the issue, the user's environment will be set as described above. The setting of RZ_START, RZ_END, etc. and $4 to the report script remains unchanged. E-mail addresses specified in the Permissions file will now expand environment parameters. This will allow users to e-mail directly to addresses that appear in fields on the form. For example, if the field Responsibility contains e-mail addresses, the entry $RAZOR_ATTR_Responsibility in the Permissions file will send e-mail to those shown in that field. If the database is using more than one issues group, the group name will now appear on the main dialog of the issues tool. Submitting issues via e-mail will honor the Razor_notice file if created. The contents of the Razor_notice file created by the before script will be output and available in the e-mail returned by rz_mail_issue_catcher. The drag-n-drop icon will only appear on the issues main dialog if the user is also using version control (versions) and/or release management (threads). Please note that drag-n-drop functionality is not available for PC client applications. Corrections: Updated rz_mail_issue_catcher to convert double quotes to single quotes in the subject line. Changed processing of Latest files to work properly in multi-platform environments where the mount point of RAZOR_UNIVERSE_DIR differs. Corrected intermittent problem with issues incorrectly displaying "Issues has recently been modified" message on an issue form. Corrected saving of filters for issues to allow different filters for different issues groups. Corrected problem with TIME_STAMP attribute on AIX with regard to Daylight Savings Time. Issues/PC: ========== The following resources are now supported by Wdefaults: Issues.IssueForm*WorkForm.populateOffset Issues.IssueForm*WorkForm.initialOffset Issues.IssueForm*WorkForm.labelWidthIncrement Issues.IssueForm*WorkForm.resizeLabels Corrected text field widths in Windows client app GUI's to allow spacing for specified widths. Limited prefix setting of new issue groups to be an alpha character. Setting of RAZOR_GROUP for non-default issues group has been corrected. Corrected issues to correctly disable Review/Modify if a newly created issue that is still displayed is modified by another issues program. Versions: ========= New functionality: The role RAZOR_ADMIN will be allowed to uncheck or checkin files if defined in the file 'Roles'. Added accelerators to the File pulldown menu for the options Rename and New folder. Added functionality to associate issues with "revert" and included a description area. The filename (including folder name, if applicable) now appears in the title bar of the dialog. Added capability to control keyword expansion on a file by file basis. The HPUX version of RCS does not honor control of keyword expansion, therefore, the control of keywords will not be honored if the database server is running on HPUX. Changed the display of thread and issues groups in the group pulldown to be a pullright menu option. Modified the Tool Properties dialog to allow hiding of issues groups. Modified the Tool Properties dialog to make hiding of thread or issues groups take effect immediately. The capability has been added to "clear" the information in the following version control dialogs: checkout, checkin and branch. Corrections: Corrected inconsistency in displaying branches. When changing file groups, the setting of Modified Range on the filter dialog will be honored. Relative to use of Option FileCheckIn: corrrected problem of updating change information prior to determining success or failure of attached before scripts. Selecting Promote when there is no STATE attribute defined will no longer be possible. A branch may not be terminated if it has a branch. Corrected problem of SCCS keyword expansion during revert operation. The before script for an uncheckout will now receive the current version of the file rather than the version that it would have become. Versions/PC: ============ Enhanced the file chooser used when comparing files via the Windows client application. Files checked-in from Versions/PC with "Leave readonly" option now properly honor the "Get file in UNIX text format" tool property. Differences may only be executed against non-binary files. Threads: ======== New functionality: Added ability to display days since last modified. The Action template has been updated to include extract_thread.apply. Corrected to allow promotion functionality. On the Generate Script dialog the field "Base directory" has been changed to "Extract thread to". Corrections: Updated to better handle file removal/renames which occur during an edit operation. Execute permission now honored during thread extraction. Terminated files associated with issues will not be included in threads updated based on issues. Will now block updates during thread extraction to avoid data conflicts. Corrected problem of some files in folders not being included in a thread. Made adjustments in compare to handle renamed files. Corrected problem in threads where not all included files were being properly displayed. Corrected problem related to including files based on issues when filenames contain spaces. Threads/PC: =========== Thread extraction now correctly honors setting for UNIX text format. Command Line Interface: ======================= New functionality: New option added to command line interface to allow users to send the output of the get or get_issue command to stdout by using the -z flag. Added the command, "new_folder", to the razor command line interface to create a folder in a file control group. Added the command, "new_thread", to the razor command line interface to create a thread. Optional major release number added to bump: razor -c bump -f -g -t [-r <new major>] [-i <issue[:<issue group>]>] Corrections: Updated before script processing for the 'razor' command to prevent reference to log file when a Razor_notice file is created. Corrected problem of an issue appearing on the incorrect machine when using the command line interface "razor popup_issue <#>". When promoting an issue via the command line, the modify.apply action will be invoked if set and the action will be set to PROMOTE_BEFORE or PROMOTE_AFTER. Modified command line thread comparison to remove temporary LEFT and RIGHT files. Corrected commandline modify of thread and thread compares when folder names contain special characters. Updated example script display_issues to use a platform independent syntax for the SCCS get command. Updated the command line uncheckout to set RAZOR_ISSUES to the issues related during the check out operation. Corrected problem when comparing 2 threads when no version has been specified. Corrected a problem executing an AFTER script for a file introduction. Scripts: ======== The following functionality has been added to rz_html_utils: insert a line, start a preformatted paragraph, end a preformatted paragraph, and set font size and characteristics. The script rz_toolbox now identifies issues that do not use the default prefix. The scripts get_associated_issues and rz_toolbox now check for all file control actions that may be associated with an issue. IssueWeaver: ============ NOTE=> If your web server is installed on AIX or IRIX, the environment variable TZ (time zone) may not be set for all applications. To insure that the time zone variable is set when IssueWeaver is executing, add the following to the script 'issue_weaver' that has been placed in the cgi-bin directory AFTER you have upgraded your current IssueWeaver installation: TZ=<your time zone setting, i.e. EST5EDT> export TZ New functionality: Control of the IW logfile has been simplified with the creation of the IW_LOG rule. IW_LOG defined as YES in the rules file will cause the generation of log files in $RAZOR_UNIVERSE_DIR/Weaver. A Rules file error will occur if the UNIVERSE rule is not set. Corrections: Fixed a problem with unknown meta tag processing. Unknown meta tags will now be replaced with an undefined HTML META tag to aid HTML debugging. For example, if an IssueWeaver header.html contained the unknown meta tag <<XXX>> it will now be replaced with <META NAME="XXX" CONTENT="Undefined"> rather than being ignored. Razor requires the first TEXT_FIELD attribute (i.e. issue Title) to be non-blank. If the first TEXT_FIELD is set to READONLY via an IssueWeaver rules file, there must be a preload script to assign a value to this field or creation of new issues will not be allowed. Customized headers and footers may now be located in user specified directories. v4.1(c) - Patch 06 Threads: Corrected occasional problem of files in folders not being included in a thread. Corrected command line modification of threads, as well as, thread compare when similar folder names are included. v4.1(c) - Patch 05 IssueWeaver: It is possible to setup a rules file to only show one text area. If an issue was created using such a rules file and was then viewed via different rules file that allowed the user to see both text areas, the incorrect template file was referenced in the non-viewable text area. This has been corrected. v4.1(c) - Patch 04 NOTE=> Once again, major upgrades have been made to IssueWeaver. We suggest that current IssueWeaver users run $RAZOR_HOME/scripts/rz_iw_install after upgrading the Razor installation to 4.1c patch level 04. NOTE=> To support a variety of web servers, the IssueWeaver Razor_iw_lib directory structure must now exist as a subdirectory of the web server's HTML documents directory rather than as a subdirectory of cgi-bin. NOTE=> Startup filters for IssueWeaver must be recreated via the IssueWeaver filter function. The format has been changed to include sort functions. Razor: Corrected a memory leak that was specific to HPUX. Addressed occasional non-removal of temporary files. Corrected Mapping file rebuild processing for deleted files. In an effort to better serve our customers, we will be issuing an identification number whenever new license keys are provided (i.e. additional purchases, service renewals). We would greatly appreciate your including this identification number in all correspondence with Tower Concepts. Thanks! :) Razor/PC: The resource "filenameLength" is now honored in the Wdefaults file. Issues: Upon a change in database via issues, reload the control files for the database (i.e. Permissions, Roles, Insensitive). Added processing to prevent non-sequential generation of issues numbers Issues/PC: Added capability to include a file or find text via a popup window in the two main text areas. Corrected problem with sensitivity setting of ONE_OF_MANY_STACK attribute. Versions: Improved auto-detection of binary files. Eliminated extra blank line added to History file after the #TITLE entry when a promotion is performed. Versions/PC: Made adjustments to accommodate checking out a directory structure to the top level of a disk drive. Threads: Corrected problem caused by updating a thread based on a large number of issues. Corrected project comparison to work properly when thread names match but are from different groups. Threads/PC: Corrected problem of not being able to extract a thread to the top level of a drive. Corrected problem encountered on some PC Networks relative to extracting a thread to the top level of a Network Neighborhood. IssueWeaver: During installation, the script 'issue_weaver' is placed in the web server's CGI directory. In previous releases, a link to the executable was created in cgi-bin. Corrected usage of ATTRIBUTE ~ALL~ in rules file to handle Readonly setting. Buttons have been added to the main toolbar to allow the user to see the modification date/time (Date) and the days since last modified (Delta). Updated to support secure http servers and use of non-default server ports. The protocol is: https://<webserver>:<server port>/cgi-bin/issue_weaver. Activities related to an issue are displayed at the end of the individual issue form. A convenience link is available at the top of the form. Now supports sort options (invert sort order, sort by modification date and case insensitive matching) on the filter form. Changed format of saved filter file. Checks the setting of the environment variables REMOTE_HOST and REMOTE_ADDR to determine the client hostname. Now sets $USER to support custom report scripts. Changed the login screen title to "No username information required" if the rules VERIFY_USER and VERIFY_PASS are set to "NO". Capability has been added to Select/Unselect All issues in the main issues list. Removed usage of the executable issue_weaver_gif. Any references to this executable may be removed from the web server's cgi-bin. Performance has been significantly improved for large issues lists especially with regard to paging. Corrected problem with filter and sort where a fatal exception would occasionally occur. Text wrap in the two separate text areas will be performed based on the TEXT_WIDTH setting. Incorporated the use of IW_valid_users_file to be setup by IssueWeaver administration personnel to avoid passing UNIX passwords across network and to allow access to users who do not have UNIX accounts. Modifications to existing issues may be submitted to the database server via the "Apply" button. The following new rules are now supported (refer to the default rules file (Razor_iw_lib/rules) for usage: STYLE One of three styles* (blocks, steno, wood) FONT HTML font tag to define typeface, size & color META User defined data which may be referenced in header/footer HTML TEXT_WIDTH Width setting for text areas TEXT_HEIGHT Height setting for text areas *To enhance the look of IssueWeaver, we now provide three styles: blocks A Q-bert style blue blocks with a black background steno A white steno pad with a handwritten style wood A wood paneling effect To change the style, change the new rule STYLE to one of the above. The default setting is blocks. You should also change the associated rule FONT to define color. We recommend white for blocks, blue or red for steno, and yellow or red for wood. Meta tags are special symbols that are automatically expanded by IssueWeaver during the generation of displays. These tags may be referenced in the header and footer files. The following Meta tags are supported: Meta tag Description ======== =========== RAZOR_ISSUE current issue number RAZOR_ISSUE_NUMBER current issue number RAZOR_ISSUE_VERSION current issue version RAZOR_ISSUE_GROUP current issues group RAZOR_UNIVERSE issues database ($RAZOR_UNIVERSE_DIR) RAZOR_USER name of the IssueWeaver user TODAY current date Users may define their own Meta tags through the use of the META rule. Login will use the first non-blank word as the user name. Improved error message when connection is being attempted to a database server that is not currently running. Corrected results when CLUSTER_SIZE is set to "0". Navigation buttons will be insensitive or not displayed if selecting one does not provide additional information. For instance, if the user is currently at the "bottom" of the main list of issues, the "Next" and "End of List" buttons will be insensitive for the blocks style or not displayed for the wood style. In cases where the user is not allowed to create a new issue (i.e. the rule FORM_READONLY is YES), either the NEW button will not be displayed or an insensitive NEW button will be displayed. Database Permissions settings are now honored. If the form is set to readonly, users will not be allowed to create new issues. Corrected random problem of not being able to submit new issues. v4.1(c) NOTE=> Upgrades have been made to IssueWeaver. We suggest that current IssueWeaver users run $RAZOR_HOME/scripts/rz_iw_install after upgrading the Razor installation to 4.1c. NOTE=> The file Thread_script_template.sh was modified to do a better job when filenames contain spaces. Users who have such files should replace the file Thread_script_template.sh in: $RAZOR_UNIVERSE_DIR/DOMAIN_01/<group>::Threads/Tables with the one that is in: $RAZOR_HOME/templates/Threads_tables_templates Added a 3rd parameter to the uncheckout before script to indicate the following: 0 - User selected 'Ok' 1 - User selected 'Readonly' Added capability to extract threads directly from the gui. Corrected project and thread diff to avoid problems when run on some operating systems. Enhanced the license manager, database server and all apps to avoid version mismatch problems. If the release number is incremented during a thread or project save, the environment parameter RAZOR_INCREMENT_RELEASE will be set to 1. Corrected threads to properly handle CHECK_BOX attributes. Corrected DEC Alpha applications to use proper sized messages. Added ability for IssueWeaver to honor readonly field settings. Corrected DEC Alpha database server to prevent problems determining VCS_DIR when creating folders. Corrected script editing for DEC Alpha. Updated razor 'bump' command to work properly with BINARY files. Added a SEPARATOR tag to the Commands and Reports files in issues to allow for a visual separator between entries. Enhanced IssueWeaver to allow fields to contain ", &, <, >. Added new Xdefault settings to control the default behavior of the versions diff output. The 3 resources are defined as the following. Note that you should only set ONE of these values. The default settings are shown. Versions*ShowAll.set: True Versions*NoIdenticalLines.set: False Versions*OnlyLeftSide.set: False Added a Save button to the versions diff dialog. Added support for predefined options in an Options file. This file can exist in either the group Tables directory or the RAZOR_UNIVERSE/Tables directory. Settings in the group Tables directory will take precedence. Options are defined in the files as <Option> <Value> pairs. Added detection of unchanged files to version control checkin process via the Options file. Users now have the option to disallow checkin's of unchanged files. Corrected problem created when no STATE attributes are defined. Added Bourne shell functions in new file rz_html_utils. This is intended to assist users who would prefer to create HTML output for reports. Corrected command line interface "rm_folder" to handle previously renamed or deleted files. Extended length of TIME_STAMP field in IssueWeaver. Enabled Save button after importing a thread into an existing thread (thread & project imports). Spaces in attribute labels are now handled by rz_utils. Corrected issues Permissions file processing to work properly when restricting who is allowed to create new issues. PC Client login panel now identifies which tool is being invoked. Corrected the reload Actions, roles and insensitive info when changing databases within the issues tool. Added capability to attach before/after scripts to terminate branch in versions. Added expansion of path to Generate Script dialog 'Output script to:' field upon selection of Ok or Apply. Corrected readonly attribute processing in IssueWeaver. Added support of ".cgi" extensions to IssueWeaver executables caused by the behavior of some web browsers. Corrected problem of edit threads exiting when a selected thread is locked. Improved warning message when an application disconnects during an introduction or modification operation. When there is a communication error, the database server will now disconnect the offending client and continue rather than exit completely. Added support to better handle rename and removal of filenames that contain spaces. Eliminated defunct processes created by the database server when running IssueWeaver. Corrected dialog title for Errors/Warnings on Windows client apps. Enhanced the Windows client app to honor Versions*FileControl settings (refer to Wdefaults). Corrected case sensitive conversion of regular expressions. Corrected the way the TIME_STAMP attribute worked in the versions filter panel for the Windows client app. Corrected IssueWeaver to honor the clearing of fields that were previously set. Revised the IssueWeaver installation process. Versions/Threads - Corrected double-click in issue lists to work properly with non-default issue groups. v4.1(b) - Patch 03 Corrected Dec alpha applications to use proper sized messages. Corrected threads to properly handle CHECK_BOX attributes. v4.1(b) - Patch 02 Added the ability for issues to start up without having a default issues group. This requires the user to use the -group flag when starting issues to specify the startup group to use. Modified rz_inject and rz_inject_rcs to disallow injection of files that are checked out. Corrected rz_issue_submit and rz_issue_modify for HP and OSF platforms. v4.1(b) - Patch 01 Corrected issues and rz_vcs to better handle issue creation on some platforms. v4.1(b) NOTE=> Changed use of sed in forward.master and create_remote.slave. All remote database users should re-run rz_install_remotes to take advantage of these fixes. NOTE=> To avoid conflicts with X, the -g flag honored by versions, issues and threads has been changed to -group. NOTE=> The BINARY attribute has been replaced by a radio group containing 'Binary' and 'Auto-detect' options on the file introduction dialog. Those who used a BINARY attribute do not need to make any changes other than notifying users that to define a file as being BINARY they must now select the 'Binary' toggle on the file introduction dialog rather than selecting the attribute defined as BINARY. Users may also take advantage of the 'Auto-detect' option which, when selected, will automatically determine whether or not the file should be treated as binary. Since they are now obsoleted, BINARY attributes will not appear in the attributes window on the versions and thread edit display filter panels as well as the versions file properties panel. Instead, an additional Binary filtering criteria has been added the the filter panels and binary indicator has been added to the file properties panel. A fifth parameter ($5) has been made available to the intro.before script in versions which will indicate if the file is being introduced as binary or not. A value of 1 indicates binary. A value of 0 indicates non-binary. Added a '-b' option to the razor command line application (razor) which is valid with the intro command. When provided this option indicates the file is to be introduced as binary. Added a new set of script functions to make script writing much easier: $RAZOR_HOME/scripts/rz_utils Simply 'dotting' this file into your Bourne shell script will make all of the functions available. To correct a bug in OpenWindows on SunOS, users with this configuration should set the following in their $HOME/.Xdefaults file: Issues.adjustFormScrollbar: False This will prevent OpenWindows from exiting after bringing up an issue form that had been previously scrolled. Corrected threads to allow users to generate a script when creating a new thread (and before the thread is saved). This will NOT allow users to create a script from an unsaved thread, the application just won't exit as it had before. Modified the command line interface to update the TIME_CHECKED_IN flag when performing a bump, thread edit or project edit operation. Modified threads to reference renamed branch file names properly. Enhanced rz_inject and rz_inject_rcs to put old vcs files into Archive/SCCS.orig (or Archive/RZ_VCS.orig for RCS). The View menu option for versions has been updated to add the following: Open All Select All in Folder Renamed the 'Clear All Selections' string in the View menu, hidden popup in main list and issue relationship scrolling lists of versions to 'Unselect All Items'. Enhanced the 'Edit File Props' dialog to select the highest state of the current file version rather than always the first state. Modified the scripts rz_rename_attr, rz_rename_attr_val and rz_remove_attr to better handle file hierarchies. Changed the name calculation in rz_inject so as to avoid problems when users set the :M: flag. Modified rz_issue_submit and rz_issue_modify to behave better on IRIX, HPUX, AIX, and OSF as it relates to setuid. The Reset button on issues will now honor the ProblemToBottom and SolutionToBottom resources. Corrected Project diff output. Modified the Mapping file update process during startup. Entries which must be added will now be queued and all updates will occur AFTER the database has been read. Added new command line option to versions, issues & threads to control whether the applications will attempt to use their default color preferences. If the flag -no_colors is passed to any applications, they will make no attempt to set background, foreground or menu bar colors. Added support for the -i flag in the 'razor' commands 'rm' and 'rm_folder'. This allows users to tie one or more issues to the remove operation. Added a new tag REMOVE which will appear in the Activity file when an issue is related to a file or folder remove operation. Corrected the 'razor' program to honor the description entered when using the -p flag. Added ability to use an alternate compress & zcat functions for binary files. If the file $RAZOR_UNIVERSE_DIR/Scripts/compress exists and is executable, it will be used for compressing binary files. The parameters passed to compress are: $1 -> -f $2 -> filename Similarly, if $RAZOR_UNIVERSE_DIR/Scripts/zcat exists and is executable it will be used to uncompress binary files. Output MUST be sent to stdout. The parameter passed to zcat is: $1 -> filename Added a new Xresource which will postpone receipt of updates in issues until a modification or creation has completed. The default setting is: Issues.updateDuringModify: True Setting this value to True will postpone updates as described above. Corrected command line thread modify functionality to eliminate intermittant problems when running on Solaris (and possibly others). Added additional processing to the rz_server to prevent unnecessary locks to remain on threads when unusual exit conditions occur in threads. Modified folder rename processing to honor existing execute settings. Corrected processing of Insensitive settings to properly honor issue group changes. Modified BINARY file processing to not require write permission to the BINARY directory when getting a READONLY copy of a file. Corrected command line interface of promotion of files to honor roles. v4.1(a) - Patch 01 NOTE=> By popular demand, added a new Action for folder removal. When a folder is removed the action specified as 'remove_folder' will be executed if defined in the Actions file. The 'remove' action will ONLY be invoked for file removals. The RAZOR_ACTION environment parameter will be set to REMOVE_FOLDER_BEFORE and REMOVE_FOLDER_AFTER for the before and after scripts respectively. The 'remove' action can be referred to by any of the following tags in the Actions file: remove delete remove.apply delete.apply Modified the introduce.after $3 parameter to properly pass the introduction directory when trees are being introduced. Modified the introduce operation to prevent introduction of files with name formats used internally by Razor. Updated the version number computation to better handle odd output conditions from rz_vcs. By customer request modified rz_add_group and rz_add_issues_group to recursively copy the templates directory when creating a new group. Modified the command line thread edit to include file id in resulting thread file. Corrected versions to hide project groups when hide thread groups is selected in the file properties dialog. Modified threads to allow users to use ++PROJECT++ as the startup group. Corrected the command line project edit feature to properly format project files. Enhanced the internal return code processing (rz_system()). Enhanced the rz_win_kid remote startup script to allow users to create a file $HOME/.razor_remote file to define system parameters (paths, environment, etc). The format of this file is Bourne/Korn shell syntax. Corrected Role processing to properly parse multi-role definitions. Added the ability to honor Role definitions in the versions tool. v4.1(a) NOTE=> Old databases should do the following AS THE OWNER OF THE DATABASE: cp $RAZOR_HOME/bin/rz_exec $RAZOR_UNIVERSE_DIR/rz_db_exec chmod ug+s $RAZOR_UNIVERSE_DIR/rz_db_exec NOTE=> Updated the remote database synchronization scripts to change the way they use 'sed'. Users of the remote database sync capability should run rz_install_remotes to get the latest scripts. Corrected problem caused by folders which had a sibling folder whose name contained a dash ('-'). Modified the 'razor' program to do a better job of dealing with branch files. Corrected the database synchronization scripts use of sed. Modified the rz_dirname script to remove leading /tmp_mnt from paths. v4.1 - Patch 01 Corrected the update of threads based on issues to always get the highest version of a file. Modified issues to format the issue text before forwarding it on to remote databases. Modified the promotion AFTER script to pass the version of the promotion rather than the latest version of the file. Corrected threads to prevent problems when generating thread script while using Thread_rules. Corrected problem with renaming folders that could cause problems when refreshing display. Changed the command line bump option to output a tag of BUMP rather than CHECK-IN in the History and Activity files. v4.1 NOTE=> Updated templates/Threads_tables_templates/Thread_script_template.sh to do a better job of handing renamed files. Users MUST update their copy in EACH threads group Tables directory to use this updated version. If users have not modified this file, they can simply remove it to force the use of the default version. NOTE=> Those using X/Y positioning on their issue form may find that their TEXT_FIELD attributes have shortened in length. If you do, simply add a line similar to that shown below to your database Xdefaults file to set the number of columns to the desired value: Issues.IssueForm*<attr label>.columns: n Corrected thread and project edit (for threads and razor programs) to properly update the "Active" state version. Eliminated the need to use 'nohup' when running razor_lm and rz_server under the Bourne or Korn shell. Modified the razor program to more accurately output the state value in the History file. Modified rename_attr_val, rename_attr, and remove_attr to update the Bitmaps file if necessary. Modified rename_attr_val and rename_attr to support the rename of STATE attributes. This includes the update of the Permissions file. Since remove_attr_val uses rename_attr_val STATE attribute values can now be removed. Corrected versions to properly display promotion information when promotion versions of different states match. Corrected day computation in the second time line on the time range dialog to properly compute leap year days. Updated kid_of_versions to properly remove files when they are introduced as BINARY files and the option 'Take the files' is selected. Corrected file rename to allow entry of folder names. Added an rz_ prefix to the following and moved the new file to $RAZOR_HOME/scripts: remove_attr remove_attr_val rename_attr rename_attr_val Added a README file to the $RAZOR_HOME/examples directory. Corrected rz_compare_thread and rz_update_thread to properly honor hierarchies. Modified threads and the razor command line to source the rz_prep file. Modified the "Which issue number" dialog to set focus to the entry text field. Added a Selections menu option to the thread edit dialog. This menu contains the blanket selections and issue selection options. Enhanced the threads program to allow for the inclusion of files based on issue relationships. This drag and drop interface will allow users to include files in a thread based on files which have been related to issues. There are two Xdefault settings shown below which can control the behavior of this dialog and the threads edit session to force the use of this feature. The following controls whether the inclusion of files may be based only of issue relationships Threads*onlyFromIssues: False The following controls whether changes can be made after file inclusion has been changed via the issue selection dialog: Threads*allowChangesAfterIssueInclusion: False Added support for PC clients for versions & threads. Added a horizontal scrollbar to the issues Activity dialog. Corrected processing of Permissions file to properly honor issue group changes. Corrected branching of binary files. Added the ability to compare versions of a thread or two differently named threads via the command line (razor -c thread_compare...). The output generated is the same as that generated from the threads interface. Added a new Xdefault setting to control the resizing of label widgets on an issue form. When using X/Y positiong it may be desireable for all labels to have a varying size based on the number of characters in the label. The default behavior is to have all labels be fixed width based on the longest label. To prevent this resize the following Xdefault setting will do the trick: Issues.IssueForm*WorkForm.resizeLabels: False Added an Xdefault to control the width of TEXT_FIELD attributes on the issue form. By default, TEXT_FIELDs which have a maximum length of at least 60 characters (as defined in the Attributes file) will be attached to the right edge of the issue form. Those that are less will have the number of columns set to the max length value. Now, by using the resource shown below in your Xdefaults file, the width will not be adjusted programatically. This will allow users to define their own width or columns values. Issues.IssueForm*<attr name>.adjustToEdge: False Updated issues to leave the SCCS file readonly after a modification has been completed. Moved the Delete/SCCS and Delete/BINARY directories to Delete/Archive/SCCS and Delete/Archive/BINARY. The database server will check this at startup and move/create directories as necessary. Corrected threads and 'razor -c get' to properly handle deleted files. Corrected the AFTER scripts in versions to send the filename rather than the branch filename when branch files are operated on. Added Role definition capability. This allows users to define role names and refernce these role names in the Permissions file by prefixing the role name with a '%'. Roles are defined in $RAZOR_UNIVERSE_DIR/DOMAIN_01/<issue_group>/Tables/Roles - OR - $RAZOR_UNIVERSE_DIR/Tables/Roles The <issue_group>/Tables/Roles file entries will override the $RAZOR_UNIVERSE_DIR/Tables/Roles entries. Role definitions can be any combination of user id, group id (preceeded by a '+') or other roles (preceeded by a '%'); Role definitions in the Permissions file may be used for either the state transition 'who' or the email column. For email, group names defined for the role will be ignored. Added a razor_folders() function to rz_toolbox. This function will set RAZOR_FOLDERS with the name of all folders in the group. Enhanced rz_toolbox function razor_files() to run more efficiently. Added support to the versions user defined scripts capability to allow users to suppress the result text dialog if the command generated no output. If the flag -supress_cmd_output is added to the user defined command, the output dialog will not appear unless the script actually generated output. Added two new X resources to the ONE_OF_MANY_STACK. These resources control the distance from the left and top of the stack to its related label. The default settings are: Issues.IssueForm*stackLeftOffset: -13 Issues.IssueForm*stackTopOffset: -5 Added new scripts rz_install_email_catcher and rz_install_email_query to make it easier for users to update the rz_mail_issue_catcher and rz_query scripts in their database. Corrected issues to properly remove tmp files when a before script returns a non-zero value. Corrected rz_vcs.rcs to remove /tmp files after an uncheckout commands. Corrected problem casued by the resource setting of Versions*OrigInfo.set: 1 in the .Xdefaults file which would cause layout problems in the check-in dialog. Added the ability to make fields insensitive (grayed out) based on settings on the issue form and user/role id. This is controlled by entries in the file: $RAZOR_UNIVERSE_DIR/DOMAIN_01/<issues group>/Tables/Insensitive Please see the following file for details on the format: $RAZOR_HOME/templates/Issues_tables_templates/Insensitive. Modified rz_new_database to reference the rz_prep.sh file in the rz_startup script as a relative path rather than an absolute path. This will prevent problems when users move their database to a new location. v4.0(b) - Patch 03 Corrected the rz_server to better handle large file descriptor limits. Modified rz_issue_submit and rz_issue_modify to set the directory permissions properly when creating a temporary SCCS directory under Solaris 2.x. Corrected the 'razor' program to properly name branch files during 'get' and 'co' operations. Modified sw_maturity_rpt and state_totals example scripts to allow users to specify issue group on command line. Modified example script sw_maturity_rpt to include overall totals. v4.0(b) - Patch 02 Modified system_setup to reference uname as /bin/uname. Modified scripts which reference dirname and basename to use $dirnameexec and $basenameexec. Corrected the razor command to honor <issue group> rather than forcing ++ISSUES++.<issue group>. Added additional checks to avoid get_info_row() warnings. Modified command line checkout and get operations to avoid requirement of having all folders (subdirectories) in existance when getting a file. Modified command line operations to use fully expanded issue names in the setting of RAZOR_ISSUES. Removed unnecessary <CR> from setting of RAZOR_FILE in the 'razor' command line program. Corrected the sorting of versions in the Diff dialog. Added email support for all issues groups instead of just the default issues group (++ISSUES++). Added support for the -g flag when starting issues. This will allow users to specify a group other than the default issues group at startup. Added support for BETA version of IssueWeaver. Enhanced introduction of folders to create any/all BINARY subdirectories requrired. This will correct any problems related to missing BINARY subdirectories. v4.0(b) - Patch 01 Corrected rz_server to properly handle files that were checked out with issues related. Corrected razor to eliminate errors generated when executing the promote_issue command. Corrected filter save option in the versions tool to prevent disabling of the default filter definition and date display function. Modified kid_of_issues to better accomodate slow connections. v4.0(b) NOTE=> For versions, the 3rd parameter passed to the following AFTER scripts will be the directory that the file was deposited, even if the file is within a hierarchy in the versions tool. checkin.apply checkout.apply readonly.apply uncheckout This means that if you want to reference the file, you should do so using a syntax such as: file=$3/`basename $1` Modified rz_add_issues_group to use the prefix of 'I' for issues groups which do not have a Prefix file when checking for uniqueness of selected prefix. Added a new X resource to issues which will allow users to change the default string used for the default issues group in the Group pulldown. The setting is: Issues.defaultGroupString: -Issues- Corrected problem with using the 'Paste Issues' feature of versions which would cause the operation to fail and the database server to exit. Corrected error outputs so that ./file is now /dir/file where dir is $RAZOR_TMP. Modified rz_issue_print to better handle line wraps. Added a new command, rm_folder to the razor command line interface. Changed server connection to use ip address rather than hostname. Removed the comma appended to the first parameter passed to the RENAME before script. Added a second parameter to the RENAME after script which indicates the old filename. $1 will contain the name as it appears in the database and $2 will contain the name prior to the rename. Added the capability to use group names in the Permissions file when defining who can move from one state to another. Group names are distinguished from user names by adding a plus symbol (+) in front of the group name. For example, to allow all users in the razor group to have permission to move from one state to another, the entry would be specified as +razor. Updated the razor_learn() function in rz_toolbox to properly handle branch files. Modified rz_toolbox to always use 'return' rather than exit when errors are found. It is up to the user to check the return status and take appropriate actions. Modified the versions diff dialog to include all versions of a file (including branch versions) rather than just those for the trunk or branch. Improved the output of the threads diff dialog. Added a 'Save...' button to the threads diff dialog. Improved the razor_lm startup process for Digital Unix platforms. Corrected problem with text match result output. Added 'Close ALL' option to versions and threads. Corrected refresh problem in the thread edit dialog. Added the ability to control filtering of states in versions and threads. By default, if a file or thread EVER attained a selected state, a filter match is made. You can now change this behavior so that a match is made only if the current version of the file is at the selected state. This behavior is controlled by the Xdefault setting. Setting it to True will match current version states only. Versions.filterOnCurrentState: False Threads.filterOnCurrentState: False Corrected miscellaneous file/folder rename oddities. Modified rz_issue_modify to do a better job of cleaning up temporary files. The execute permissions of files will be saved when they are introduced and reset when checking out or getting readonly copies. This capability will be controlled by the setting of the execute bits on the related Info file in the database or via the 'Edit File Props' dialog. Corrected the command line interface to properly honor the directory name when checking a file in or out. Specifying a directory will put the file there, even if it is within a hierarchy. Added the ability to specify that a checkout, checkin or get readonly operation should not honor the file hierarchy. By selecting the toggle 'Path is absolute' the file will be placed in the specified directory and will not duplicate the hierarchy. The initial setting of this toggle button can be controlled by the Xdefault setting: Versions*AbsolutePath.set: False Made modification to versions to better handle files which contain an "@" symbol in their name. Modified command line promote to properly log related issues into the Info and issues Activity files. Corrected the introduce operation so that when introducing a file into a folder and selecting 'Checkout for edit' will not duplicate the folder structure. Improved the performance of thread script generation. When relating issues, the setting of RAZOR_ISSUES will vary depending on which issue group each issue comes from. If it comes from the default group, the issue name in the list will appear as in previous versions, simply the issue name. If the issue comes from a different issue group, the group name as it appears on the issues Groups pulldown (ie name sans ++ISSUES++.) will be appended to the issues name in the form: <issue name>:<issue group name> User scripts may have to be modified when adding other issue groups. The issue name passed to the various command line functions must follow the form: <issue name>:<issue group name> when referencing issues from issue groups other than the default issue group. The value of <issue group name> is the same value as appears in the Groups pulldown of the issues tool. v4.0(a) Corrected RCS version of rz_vcs to properly use RZ_NEW_NAME. This change will make sdiff work correctly when using RCS. Modified the Uncheckout operation to honor user selection of the Stop button on the status dialog. Corrected versions to properly handle the attachment of multiple bitmaps. This fix eliminates the generation of the BadDrawable error. Corrected rz_inject to handle SCCS files which do not start with v1.1. Corrected razor_lm on DEC Alpha to properly determine if the other razor_lm processes are running (again). Added control to change the behavior of STATE bitmaps in the versions program. The bitmap shown can represent either the highest state the current version of the file has attained or the highest state ever attained (default). For users who prefer STATE bitmaps to display the highest state of the latest version, the following entry should be placed in the file $RAZOR_UNIVERSE_DIR/Xdefaults: Versions.displayHighestStateEver: False Corrected output of id value in 'razor license' for HPUX. Corrected the attachment of the Apply, Cancel and File buttons on the Diff dialog so that the file text field will not overlap on some platforms depending on font selections. Added a branch command to the razor command line program for the creation of branches. The output of this command will be the version number of the new branch. Added the capability to execute a script when a file in the thread edit dialog is double-clicked. If the entry 'double-click' appears in the Actions file for the file group, the script specified in column 2 will be executed. The parameters passed to the script are (in order) filename, current version, included version (set to NONE if file is not included in thread) and a flag set to 1 if the file is included, 0 if it is excluded. Added the ability to have groups of issues. The script rz_add_issues_group will allow users to add additional issues groups to their database. Corrected the command line file promotion to properly honor an asterisk in the Promoters file. v4.0 - Patch 04 Corrected versions check-in operation so that when the "Check files back out for edit" is selected, the file is properly obtained from the archive. Corrected the razor 'bump' command to work properly with hierarchies. v4.0 - Patch 03 Removed generation of invalid error message from 'razor' commands. Fixed versions diff to work properly when options are changed and the Apply button is re-selected. Corrected computation of id on DEC Alpha. Corrected razor_lm on DEC Alpha to properly determine if the other razor_lm processes are running. v4.0 - Patch 02 Modified all applications to more consistently honor the setting of RAZOR_TMP. Modified the rz_issue_summarize reporting scripts to remove only trailing commas from attribute values. Modified the icon for the issues filter dialog. Modified the issues program to display the proper information in the text panels when a user performs the following sequence: Toggle 'Modify' on the form Modify the issue Select 'Apply' Toggle 'Modify' Toggle 'Review' Corrected kid_of_versions so that sdiff works properly on all supported platforms. Modified rz_inject and rz_inject_rcs to allow users to run them several times without potentially confusing the database files. Changed error message when server finds mismatches in Mapping file. Added execution of before script for thread duplication command. Modified file introductions so that introducing into a folder and leaving a readonly copy will leave a readonly copy of the file in the original destination rather than in a hierarchy below the intro directory. Changed the way 'zcat' is invoked for binary files by removing subshell. Apparently some platforms did not appreciate the previous approach. :-( Corrected the razor program which was incorrectly generating errors of duplicate filenames during thread and project edit operations. Modified rz_toolbox to use $nawkexec rather than nawk. Corrected issues bug which will cause application to exit under certain modify conditions which contain X_OF_MANY attrs. Corrected versions introduction so that using the Apply/Cancel combination will properly show introduced files that went into open folders. Disabled the Rename and New Folder buttons for non-file groups when using versions. Modified the Rename and New Folder dialogs to disallow iconification. (is that a word?) Corrected problem on Solaris platform which would make the Rename and New Folder dialog text area unwriteable after changing groups. The net effect is that changing groups is now faster. Added command line introduction of files. For the Issues/PC client, removed 30K text size limitation on the Issue form text panes. For the Issues/PC client, corrected arrangement of rows in X_OF_MANY fields. For the Issues/PC client, retain last position of the Issue list and Filter panel so they assume that position when Issues is restarted. For the Issues/PC client, added a menu to the Razor desktop window. Any number of instances of Issues may be started from the desktop menu. As well, any number of independant Razor desktops may be active at one time. The Razor desktop has been added to the Start menu. v4.0 - Patch 01 Disallow introduction of .. directory. Corrected Solaris 2.4 rz_server to handle PC issues client. Corrected razor_learn() and razor_files() in rz_toolbox to handle hierarchies. The 'razor' command line program will set the environment parameter RAZOR_CMD_LINE so that user scripts can easily distinguish between GUI and command line operations. Corrected the Rename function in the versions program so that folders and files within folders are properly handled. v4.0 NOTE=> You must run the new script update_state_dates in order to convert your Issues STATE entries to 4 digit year values. This script will only need to be run one time and will update your Info files. Backup copies of all Info files will be made by the script as a precaution. NOTE=> In order to support file renames, the Thread_script_template.sh has been modified. Users MUST place this file (located in $RAZOR_HOME/templates/Threads_tables_templates) into the Tables directory of each Threads group. Added support for hierarchies within the versions tool. This feature will allow entire directory trees to be replicated within a single Razor group. Added an issues client for Windows NT/95. Enhanced (decreased) startup time of issues, versions & threads. Made mod to honor default setting of CHECK_BOX and BINARY attributes. Added check_server_down() function to rz_toolbox. It will return 1 if the server is down, 0 if it is not. Made the environment parameter RAZOR_INFO_FILE available to the edit_props BEFORE script. This file will contain a a temporary info file describing the attribute settings. The versions diff panel will now display a notice when the files do not differ. Modified report scripts which referenced Title to look for it in the first ATTRIBUTE setting. This will make the report scripts more flexible to changes to attributes. Modified error log dialogs to eliminate redundant notice dialogs when a Razor_notice file exists. Change default behavior of versions to hide thread groups rather than show thread groups. Added a new resource Issues.stateNameLen to allow STATE labels to be longer (or shorter) than the default of 15. Added a new resource showOccam to control the display of Occam the Icon on the status and error log dialogs. Setting it to False will cause Occam to be replaced with a generic Tower Concepts icon. Added the ability to control where tmp files are created. By default they are in /tmp. Setting RAZOR_TMP to an alternate directory which is writeable by the user will change this behavior. Added a Stop button to the status dialog to allow users to halt an operation. Note that the current operation will be completed but the remaining will not. Added before/after processing capability to the remove command line command. The Actions file entry for this action is REMOVE.APPLY. Modified the time entry interface to use 4 digits for the year rather than 2. Added 4th field to thread script get_file() call which indicates if the file is BINARY. Added an Ok button to the versions Introduce dialog. Removed the rz_vcs.hpux, rz_vcs.aix and rz_vcs.dux scripts and replaced them with a generic rz_vcs script. Modified the file introduction panel to accept extended selection using the middle mouse button. This behavior mimics that of the main list in issues, versions & threads. Returning a 99 in the introduce BEFORE script will cause the file/folder to be skipped. This return code will not generate a Razor error log. Added the ability to set file attributes during file introduction. By outputing Attribute/Value pairs (tab separated) into the file $RAZOR_ATTR_FILE (note that RAZOR_ATTR_FILE is SET by Razor), the file attributes set by the user can be overriden. This must be part of the introduce BEFORE script processing. Designation of Binary files must be done by setting both the BINARY attribute value as well as creating the file $RAZOR_TMP/RAZOR_BINARY.$RAZOR_PID. Note that this capability can NOT be used to set State attributes. When checking a file out for edit or readonly, if the file already exists in the destination directory, the execute permission of the new file will be set to be the same as that of the existing file. When checking a file back in, if the option leave a readonly copy or check back our for edit is selected, the execute permissions on the new file will be the same as that of the original. Added the ability to have database configurable templates which are used when creating new groups. If the directory $RAZOR_UNIVERSE_DIR/templates exists, all versions and threads templates will be taken from this area. The string output during a state transition can have information appended by creating a script in the .../++ISSUES++/Scripts directory named rz_state_string. The script will receive the date string and the user id as input parameters. The first 64 characters output by the script will be appended to the state information. Added the ability to rename files without upsetting thread definitions. v3.5(e) NOTE=> Modified the following scripts to execute much faster. The name flag MUST be added to the file: $RAZOR_UNIVERSE_DIR/DOMAIN_01/++ISSUES++/Tables/Reports for each entry which references one of these scripts: rz_issue_summarize rz_issue_display_titles rz_issue_print_titles rz_issue_summarize_short rz_issue_print rz_issue_print_short rz_issue_status.rpt Modified rz_issue_print_short to output title information. Added new script rz_issue_summarize_file which will process an issue file specified and generate output very similar to rz_issue_summarize. Modified rz_issue_mod_mail and rz_issue_intro_mail to take advantage of the the rz_issue_summarize_file. Modified the system_setup file to allow for more flexibility in configuring print options. Corrected command line thread option to clean up log file when complete. Corrected versions program to elimiate a problem selecting version values on the diff, checkout readonly and browse dialogs. Modified the rz_learn and rz_learn_file functions in rz_toolbox to handle groups with no STATE attributes. Modified issues to remove temporary list file after running a command from the Commands pulldown. Modified versions, issues & threads to remove log files after AFTER scripts complete. Added capability to Thread & Project population script to include commands to execute AFTER the population of files/threads is complete. For Thread groups, the file Thread_script_after_template.sh should be placed into the Tables directory for the Thread group. For Projects, the file Project_script_after_template.sh should be placed into the Tables directory of the ++PROJECT++ group. Modified rz_add_group to remove Threads specific config files when creating a Project group. When using the command line interface, Razor_notice files generated by BEFORE scripts will be sent to the display when an error occurs. Added two new X resource settings to issues which will set the initial scrollbar position of the issue form text widgets (commonly referred to as the problem text and solution text). By default, the scrollbar will be at the top of the text widget, to set them to appear at the bottom: Issues.problemToBottom: True Issues.solutionToBottom: True Modified error output of chooser functions. Modified the razor command line thread script generation function so that only 1 license token is required rather than 2. New issue forms (for issue creation) will have their scrollbars reset. Modified rz_vcs and rz_vcs.sccs to correct an oddity which occurs when introducing files on IRIX systems. Corrected check-in problem caused when many lines of text are entered at check-out time into the text area and the "Use original info" toggle is enabled for the check-in operation. The issues program will no longer do an unnecessary get when executing a Report configured with the name option. Modified the razor command line to enforce database write permissions when deleting files and issues. Only those with write permission into the Info, History, Archive/SCCS, Delete/Archive/Info, Delete/Archive/History and Delete/Archive/SCCS will be allowed to delete. Added drag & drop support between issues and versions/threads. Added X resource enableDnd. The default value of this parameter is True as shown below. It can be set to False to disable the drag & drop behavior. Issues.enableDnd: True Added X resource enableCopy. The default value of this parameter is True as shown below. It can be set to False to disable the copy issues capability. Issues.enableCopy: True Added automatic inclusion of X nls patch for SunOS and Solaris. Renamed Razor defined X resouce Offset to be populateOffset. Added toolbar to issues. Added two example scripts mail_issue_changes and summarize_files. See the header of these scripts for details. Per customer request, added dots_6.xbm to the glyphs collection. Disabled the ability to introduce files into the ++PROJECT++ group. Modified versions to properly handle double quotes in the title line. Invalid time settings on Solaris, SGI, HP and OSF systems will generate the proper error so that an error notice is displayed. Removed double quotes surrounding the RAZOR_ISSUE environment parameter set by versions & threads. Removed <CR> in setting of RAZOR_TITLE parameter in versions and threads. When switching databases, the hidden popup on the main list is now being properly re-enabled. Modified rz_server to ignore SIG_WINCH to slightly improve performance. Modified issues to more gracefully handle switching to a database which is not running. Added an email composition dialog to the Email to Support button on the error log dialog. Also added an Email Comments button to the Help pulldown on the menu bar of the main window for issues, versions & threads. Default "To:", "Subject:" and "Cc:" fields may be changed through Xdefaults settings. Obsoleted the rz_mail_error_log script and replaced it with rz_mail_comments to go with the new email composition dialogs. Corrected calculation of id value for OSF platform. Corrected command line promote to allow promotion of threads. Corrected invalid row warning output message. Modified command line issue promote to create temporary issue file for the BEFORE script. Added the ability to duplicate a thread via command line. Added the ability to bump the major version of a file via the command line. Modified the database server to handle long description areas in versions & threads. v3.5(d) Added support for the Solaris/x86 and DEC Alpha (OSF/1 3.x) platforms. Changed the number of columns used to display days on the time entry dialog so that 7 days appear in each row. When browsing a project, the project file will be removed from /tmp after it has been loaded. Added thread and project editing using the 'razor' command line. Corrected the time range filtering of issues to set HH:MM:SS to 00:00:00 for the from time and 23:59:59 for the after time if the time format does not contain a time component. Modified focus setting during file introduction to eliminate X errors if window is iconified and to prevent removal of focus from other windows. Renamed File_attr_desc to be Attributes. Both file names will be honored with the Attributes file taking precedence over the File_attr_desc file. Modified the error log so that the text is scrolled to the bottom of the text where the most informative data is located. Added a 4th parameter to the checkin.BEFORE script to indicate what action the user chose (0=Take files, 1=Leave Readonly, 2=Checkout) Corrected a problem which existed on some platforms when using the 'razor -c get' command. v3.5(c) - Patch 01 Modified kid_of_versions to properly browse Project files when RCS is used. Corrected the versions program so that setting the makeBackup resource to False does not cause problems at invocation. Modified kid_of_versions to properly execute the BEFORE script for edit file props and promote. Corrected threads to prevent edit mode when another user is modifying the same thread. Corrected the attachment of bitmaps so that if the first bitmap is not defined, the other bitmaps will still appear. Added the ability to introduce dot (hidden) files. Modified the command line promote to complain if a version or state is not specified. v3.5(c) NOTE=> Changed the license scheme for AIX and IRIX users. Those using these systems must contact Tower Concepts for new license keys. Modified issues to properly set TIME_STAMP fields on new forms to be editable (or not) as configured. Added a new Xdefault for versions which allows users to prevent the backup files (...filename) from being created during the checkin and introduction operations. If not set, this entry defaults to True: Versions.makeBackup: False Enhanced the text searching capability in issues to add boolean operations for keywords. Added setting of RAZOR_FILE to command line interface for use in BEFORE/AFTER scripts. Modified script output to set PROJECTDIR rather than PROJECT_DIR. Added a new parameter to the command line check-in and check-out operations. An optional '-p <file>' flag may be added to the co and ci commands. The contents of <file> will be entered as description (prose) text in the history file. Corrected exit codes of the 'razor' program to be 0 for success, and non-zero on failure. Corrected rz_vcs.rcs to properly handle 'rm' command. Modified rz_toolbox and catcher.remote.both to remove the -e option from the grep/egrep commands. Modified the Promotors file to honor an asterisk (*) to indicate anybody can perform a promotion. Renamed the Tables/Promotors file to Tables/Promoters. The old name will still be honored. The environment parameter RAZOR_TITLE will be set to the title indicated during check in, check out, branch and revert functions. This parameter will be available to the respective BEFORE and AFTER scripts. Added BEFORE/AFTER scripting to the file properties modification dialog. The entry keyword in the Actions file is file_props.apply The BEFORE and AFTER script will receive the filename and the version number of the file in parameters 1 and 2 respectively. Modified the AFTER scripting for issues, versions, threads and razor to run after the database update has completed. Changed the AFTER script parameters for an uncheckout operation. If a readonly file was obtained, $3 will be the directory it was put to. If a readonly file was not obtained, $3 will contain the string "N/A". Corrected thread project editing mode so that threads of the same name from the same group can appear only once. Added a new Xdefault setting to threads to control the number of columns used for displaying Groups. Any positive value will be honored, otherwise, the columns will be determined programatically. A sample setting in a .Xdefaults file which would use 5 columns would be: Threads.groupColumns: 5 Corrected problem in issues which occurs when new issues are created using the 'Apply' button, toggled to Modify, and then back to Review. An error 'Unable to open text...' would occur under this sequence of events. Corrected filtering of long lists of X_OF_MANY items. Added a new command 'razor id' which will output the id information necessary for license generation. Modified the check-in operation to properly set the RAZOR_ISSUES parameter when files are checked in using original information. Corrected execution of the PRELOAD script. Modified rz_issue_submit so that preload TIME_STAMP fields that are not filled at the remote site of a remote db sync setup are left blank rather than rejected. Modified issues so that failures will not reset the issue form back to the original state, but rather will leave it as is in Modify mode. Corrected problem with state transition control in issues which would allow illegal transitions under special situations. Modified rz_issue_compare to properly use the type of ATTRIBUTE when invoking 'razor compare'. Modified the rz_vcs script to allow for branching from the end node when it is already locked for edit. A new environment parameter RAZOR_ACTION has been added to define which action type is being executed. The format of the value is <operation>_BEFORE for BEFORE scripts and <operation>_AFTER for AFTER scripts. The <operation> will be one of: For versions: CHECKIN, CHECKOUT, UNCHECKOUT, PROMOTE, PROPS, BRANCH, REVERT, INTRODUCE, READONLY For issues: CREATE, MODIFY For threads: THREAD_CREATE, SAVE Corrected command line generation of thread population scripts to honor thread script template files. Modified the rz_vcs.aix script to properly honor return codes of SCCS commands. Modified all rz_vcs scripts to better handle branching. Added the ability to limit who can execute the "razor down" command. If the file $RAZOR_UNIVERSE_DIR/Admin exists, then only those users who user name appears in this file (1 name per line) will be allowed to bring the database server down. If this file does not exist, any user can execute this command. Added the ability to change the label of the "Promote..." button in the main versions window by setting the Xdefault entry: Versions.MainWindow.Promote.labelString: Promote... Modified the razor_lm to properly release all licenses when a database server is brought down. Removed the 8 character limit on the filetype field on the main versions display. Added license re-sync capability to the 'razor info' command. The filename pattern in the Diff file chooser dialog will be preloaded with the name of the file currently selected. Modified versions script processing to properly honor return codes and notice box requests. Modified thread import, script, and project thread selection dialogs to prevent editing of title field which served only to confuse. v3.5(b) Uncheckout operations will now place an entry in the Activity file of an issues related during the check-out operation. Added the ability to control whether an issue form will be dismissed via the <ESC> key. By default, pressing the <ESC> key on an issue form is the same action as selecting the Cancel button. To disable this, an entry may be placed into an Xdefaults file of the form: Issues.ignoreEscape: True Modified rz_inject_rcs to properly identify introductions with the keyword INTRODUCE rather than INTRODUCED. Modified threads to handle longer group names. Modified the thread script generation to source the rz_prep.sh file from the proper location. Modified threads to make the Project script executable upon creation. Modified rz_mail_issue_catcher to better handle time stamp inputs. Modified issues to leave TIME_STAMP fields blank if they are added to the File_attr_desc file of an existing database. Additional issue form preloading capability has been added. This capability provides the ability to preload any changeable fields on the issue form when a new issue form is requested. If a "preload" script definition appears in the Actions file as a BEFORE script, it will be executed prior to displaying a new issue form. The output of this script must be sent to the file pointed to by the environment parameter RAZOR_PRELOAD (this parameter is set by the issues program). The format of the file is a TAB separated list of attribute label/value pairs. Modified rz_issue_submit for Solaris to better handle SCCS's insistance of not honoring setuid settings. Added a new Xdefault setting to versions to control the number of columns used for displaying Groups. Any positive value will be honored, otherwise, the columns will be determined programatically. A sample setting in a .Xdefaults file which would use 5 columns would be: Versions.groupColumns: 5 Modified threads to properly display the title on the thread edit dialog when creating a new thread. Modified examples/attr_to_xy to better handle LABEL attributes. Modified rz_server to use internal stat structure so as to prevent possible communication problems between clients of different platforms. Modified rz_issue_submit to properly honor length limits of text fields. Added a new 'Checked out by:' field to the versions filter and more control over the view of branches. v3.5(a) - Patch 02 Removed the 'Glyphs' file which was a holdover from the Sun/OpenLook release. Modified the 'Bitmaps' file to use $RAZOR_HOME as the default location for the 'glyphs' directory. Updated rz_new_database to reflect changes made to the 'Glyphs' and 'Bitmaps' files. Added an rz_learn_file() function to the rz_toolbox. This function takes as input a file in an Info file format and sets environment parameters just like the razor_learn() function does. Corrected the behavior of the 'razor -c promote ...' command so that it handles version number checking properly and does not dump core on the Solaris platform. :-( Modified threads to properly handle the removal of threads. The threads tool will no longer allow users to compare, import or generate script if no threads have been created. The versions tool will now allow branches from v1.1 as well as from the latest version of the file. Modified issues so that long text fields will not be formatted in the SCCS file, causing report output to be truncated. Modified issues to set the environment parameter RAZOR_FILE_LIST rather than RAZOR_LIST_FILE when options are executed from the Commands pulldown. Modified the example script rename_attr to properly handle attribute names which contain spaces. When specifiying names with spaces, users must enclose the names in double quotes. For example, to rename the attribute 'The Priority' to 'My Priority' for your issues database, the syntax would be: rename_attr ++ISSUES++ "The Priority" "My Priority" Added a new definition _SCCS_ADMIN_ to system_setup. Modified rz_inject to disable the 'v' flag on existing SCCS files. Modified the SCCS rz_vcs files to reference _SCCS_ADMIN_ and to enable to 'b' flag. Modified rz_issue_submit to eliminate spaces in ONE_OF_MANY attribute values. Modified rz_issue_submit and rz_issue_modify to improve the performance of email submittal and remote database synchronization. Modified issues so that empty lines are not added to the end of the Problem text area after each modification. Modified rz_issue_submit to handle longer <who> email addresses. Added two scripts to the 'examples' directory which show users how to get issue summaries and query the database for issue summaries via email. Significantly enhanced the performance of command line (razor) operations. v3.5(a) - Patch 01 Added the setting of RAZOR_GROUP and RAZOR_PID to the razor program for use by attached scripts. Modified rz_issue_submit to handle attributes with no STATE defined. Modified issues to better handle TIME_STAMP values for empty fields. The issues program will leave empty fields alone rather than put 12/31/69 into the field. This change also includes the time entry dialog. Modified the rz_server to output no time string when an empty TIME_STAMP value exists. Corrected problem with Diff function to properly recognize the return code values. v3.5(a) Added BEFORE/AFTER script processing to the Promote operation. Adding an entry into the Actions file of the form: promote.apply <tab> <script | n/a> <script | n/a> defines a script to run before and/or after the Promote operation is performed. The script defined will be pased the following parameters: $1 - Filename $2 - Version of promotion $3 - State name of promotion Added a command line Promote capability for files and issues. The syntax of the commands are: For files: razor -c promote -f <file> -v <ver> -s <state> -g <group> [-i <issue>] For issues: razor -c promote_issue -f <issue name> -s <state> Added the ability to define issue relationships on command line operations for check-in, check-out, and promote. Any number of -i <issue number> flags may be added to the command line for multiple issue definitions. A new flag '-g' has been added to the versions and threads tools to allow users to specify the starting group via the command line. A new configuration file has been added to Issues which allows users to define commands to be executed. This configuration file is named Commands and contains a tab separated list of menu label and command to be executed. If the Commands file exists and contains such a list, a Commands menu option will appear on the main Issues display. The command selected from this menu will be executed and does not require any issues to be selected from the main list. If files are selected, their names will be placed into a file pointed by the environment parameter $RAZOR_LIST_FILE. Made misc updates to the remote database parsing scripts. Users of this feature should re-run rz_install_remotes to update their setups. The paths to files defined in the configuration files named: Actions Bitmaps Commands Reports may now contain environment parameters and the '~' symbol. The Time Entry and Time Range dialogs have been re-parented. The following Xdefault settings have been made available to the issues program: To set the Filter View->Invert sort order toggle: Issues*InvertSortOrder.set: 1 To set the Filter View->Sort by modification date toggle: Issues*SortByModificationDate.set: 1 To set the Filter View->Case insensitive matching toggle: Issues*CaseInsensitiveMatching.set: 1 To set the Main menu View->Modification date toggle: Issues*ModificationDate.set: 1 To set the Main menu View->Days since last modification toggle: Issues*DaysSinceLastMod.set: 1 The following Xdefault settings have been made available to the versions program: To set the Main menu View->Modification date toggle: Versions*ModificationDate.set: 1 To set the Main menu View->Days since last modification toggle: Versions*DaysSinceLastMod.set: 1 Removed the need to use the files $RAZOR_LICENSE_DIR/License_port $RAZOR_UNIVERSE_DIR/Razor_ports This change should also eliminate those annoying |---|---|---|... messages that can appear when starting a database server. Added a new search capability to issues. This feature allows users to search the text panels of the issue form for string matches. All new databases have this feature enabled automatically. To enable this feature for existing databases, the owner of the Razor database must create the directory: $RAZOR_UNIVERSE_DIR/DOMAIN_01/++ISSUES++/Latest and then run the script: rz_issue_build_latest As a note, searching of the text areas can be time consuming. Since the search is done against the issues displayed on the main list, users should filter their display to include only the issues that are of interest. A text search capability has also been added to each Issue form to search either of the two text areas. By using the right mouse button from within either of these two areas, a 'Find...' option will appear on a popup menu. Selecting this option will pop up the 'Find' dialog. This dialog allows for searching either text area and to use standard string matching or regular expression matching. Corrected a problem loading database Xdefaults which for some platforms prevented the loading of more than just the first line of the file. This fix included honoring of key translation definitions in this file. The widget name for LABEL attributes has been changed to be the name defined in the File_attr_desc file for the LABEL. A new option has been added to the Versions, Threads, and Issues filter panels which allows users to disable the 'match while typing' feature. This feature, when active, will update the filter count shown in the left footer of the Filter panel with each keystroke. Disabling the feature will cause the Filter panel footer to be empty until the user removes focus from the text field widget using either a <TAB>, moving the mouse out of the Filter panel, or selecting something else on the Filter panel. By selecting the Filter panel Options->Match while typing toggle button, this behavior can be turned on or off. By default this value is set. To change this default, users can set the Xdefault: Issues*MatchWhileTyping.set: 0 Versions*MatchWhileTyping.set: 0 Threads*MatchWhileTyping.set: 0 Added a new option to the versions Check-in dialog which allows users to use the original check-out information for the check-in operation. This information includes the title, directory, description, and related issues. The default is to use the same information for all files (the original behavior). By setting the Xdefault value: Versions*OrigInfo.set: 1 the default will be changed to use the original check-out information for the check-in. Related to the previously described modification, selecting files in the Check-in dialog will cause their check-out information to be shown in the appropriate fields on the Check-in dialog. Double clicking on an issue number shown in the issues lists of the check-in, check-out, promote, or introduce panel will cause that issue to be displayed IF the user has issues running against the same database. When running in debug mode, the information dialog now properly contains title information indicating debug output. Changed setting of time in creation of new issues to be based on the server time. This will correct the potential of database updates not appearing on the issues main display until the application gets restarted. Added an 'exit 0' to end of rz_issue_tally to return the correct status. Issues will now indicate the action of ALTERED for issues which are modified without changing the state. The output of the 'razor' command will now include the contents of the VERSION file. Modified the rz_vcs.aix script to use the fullpath to the SCCS commands. Threads BEFORE/AFTER scripts will have the environment parameter RAZOR_ISSUES available which indicates the issues that have been related to the operation. The return code from BEFORE & AFTER scripts of versions and threads will now correctly use the actual value returned from the script. Made misc changes to the remote database sychronization scripts and executables. Modified the way the font can be set for STATE attributes. A new X resource, '*stateFont' can now be defined to set the font for STATE attributes. Remote database synchronization and submission of issues via email now supports attribute labels which contain spaces. Eliminated the condition which generates the warning: "get_info_row() - Row xx not found." Corrected a rare condition which occurs in rz_issue_submit if the environment parameter $HOME is not set. Corrected the rz_install script to properly sense the use of RCS and reconfigure an update accordingly. v3.5 - Patch 02 Added ability to define the resource: Versions.filenameLength: 32 Threads.filenameLength: 32 which sets the maximum number of characters a filename will use on the Versions main display and Threads edit display. The default value is 32 (as shown) and the maximum in 128. Users who change this value may also want to modify the resource: Versions.MainWindow.width: 660 Threads.ThreadEdit.MainForm.width: 450 from their default values shown to accomodate the filename length change. Added an Apply button to the Generate Script panel of threads. The email submittal of issues correctly handles the TIME_STAMP settings. Modified the TIME_STAMP attribute to honor the 'width' value in an Xdefaults file. Using the window manager Close menu option on the issues 'Show Activity' screen will no longer casue the application to exit on the next selection of Show Activity. Resetting new issues will no longer generate a warning message and will properly reset of two text panels. The Issues list in Versions will be correctly populated for files which have been previously unchecked out after relating Issues to the checkout operation. A new environment parameter, RAZOR_HELP_DIR has been added to support the definition of an alternate help directory. This parameter should contain a path whose contents contain a directory named help and has the same files (probably different contents) as those found in the $RAZOR_HOME/help directory. v3.5 - Patch 01 Corrected time stamp sorting. Corrected rz_install setup of 'trusted_users' file. Corrected default value of TIME_STAMP preload value to behave as documented (default = N). v3.5 Added a new field, TIME_CHECKED_IN to the database. This is available in the Info file as well as via the rz_toolbox. NOTE=> Existing users must use the script 'update_db_3.5' to bring their database up to date. To use this script, make sure that you have sourced the rz_prep file to set the proper Razor environment parameters and then simply execute update_db_3.5. The files in the Info directory for each group in the database will be udpdated. The original Info directory will be preserved as a backup and may be removed when you are satisfied that the changes were implemented. The name of the backup directory will be output when the script completes. Added "Project" capability to Threads. This allows users to define a Thread-of-Threads. Selecting the -PROJECT- group from within the Threads tool will place the user into the project definition editor. Users of new databases can use this feature immediately. Existing users must first add the PROJECT group by running rz_add_group ++PROJECT++ Added a TIME_STAMP attribute. This attributes allows users to have time (time and/or date) information represented in fields on the Issue form. The format of the entry in the File_attr_desc for the ++ISSUES++ group is: TIME_STAMP <TAB> <Label name> <TAB> <Time fmt> <TAB> <flags> The <Time fmt> follows the format described in the man pages for gmtime or ctime. An example of a <Time fmt> would be the string %D. This would display the date in the format MM/DD/YY. The <flags> are separated by commas and can be any of: I=<nn> -Defines an increment in days to be added to the current date. P=[Y|N] -Defines if this field should automatically be loaded when a new Issue is created. The default is N. R=[Y|N] -Defines if entry of the field is required. The default is N. U=[Y|N] -Defines if the field should automatically be updated when an Issue is transitioned to the modify state. The default is N. W=[Y|N] -Defines if the field is writable. The default is Y. To compliment the TIME_STAMP attribute, a new dialog has been added to the Filter and Sort panel which allows users to enter the range of dates to match. The OpenLook window manager users no longer are required to add entries to their XKeysymDB file. This allows all users to use the 3.5 series executables. The executables Issues, Versions and Threads have been renamed to be issues, versions and threads respectively to be more consistent with the rest of the world. Also renamed the Kid_of_xxx executables to be kid_of_xxx. This release contains a wrapper script for those still using the old names, but users should start using the new names to prevent future incompatibility. Moved the 'trusted_users' file from the $RAZOR_HOME/scripts directory to the $RAZOR_LICENSE_DIR directory. Sites which take advantage of the email check-out/check-in/query of files must do the following: - Move your current trusted users file to the $RAZOR_LICENSE_DIR - Have your users execute rz_mail_signup to reconfigure their environment. Modified the license manager to process an additional license key. All users of 3.4(c) will need to obtain a new Razor license. Added additional sorting capability to the issues Filter & Sort panel. Added the ability to display modification date on main issues display. Added the ability to display the days since last modification on the main issues and versions displays. Added a case insensitive matching capability to the issues filter. Added a date since field to the versions filter to allow for the display of files which have been checked in (reverted, introduced or new branch). Added issue relationship to threads create and save dialogs. Added display of descriptive text to the Import and Generate Script dialogs in the threads tool. To enhance integration with other tools, two new razor commands have been added. These commands will only operate if the user has issues already running. New issue forms may be popped up via the command: razor new_issue Existing issue forms may be displayed via the command: razor popup_issue <number> where <number> is an integer value. Added a "Save..." option to the issues Report output and Versions Script output. Added a "Email to support" button to the Error dialog. Selection of this button when an error is displayed will send email to support@tower.com. Other email addresses may be configured by modifying the new script rz_mail_error_log script. Added the abitlity to browse files within the versions tool in your editor of choice. By setting the environment parameter RAZOR_EDITOR to point to a script (most likely in each users home directory), the script will be passed the full path to the temporary file ($1) containing the contents of the file specified along with the proper name of the file ($2). A sample has been provided in $RAZOR_HOME/examples/razor_browse which will bring up the 'vi' editor in an xterm window and set the title bar to the name of the file. Note that the script must remove the file specified in $1 when the browse session completes. Added a new flag for Versions user scripts defined through the Scripts pulldown menu to allow the generation of a file containing the list of files selected. This list can include either the filenames or the filenames along with their version number depending on the flag passed. If the user script definition has the flag -list, the environment parameter $RAZOR_FILE_LIST will contain the name of a file containing the list of files selected. If the flag -list_version is specified, the environment parameter $RAZOR_FILE_LIST will contain the name of a file containing a list of filenames and versions. The file indicated in $RAZOR_FILE_LIST will contain one entry per line, where the entry is either the filename or filename and version depending on the flag passed. Issue names specified on the command line can be simply numeric values rather than the formatted I...-nnn form. Two new commands have been added to the razor command line related to issues. These new commands are simply hybrids which no longer require you to enter "-g ++ISSUES++". The commands are: razor -c get_issue -f <issue> razor -c rm_issue -f <issue> The Save panel will now become "busy" during a Save operation within threads. The database history information shown in versions using the Utilities->Info selection will scroll to the bottom of the pane. Added two issue comparison scripts, rz_issue_compare_ver and rz_issue_compare which output differences between different versions of an issue (rz_issue_compare_ver) or different files (rz_issue_compare). Moved the scripts/Tables, scripts/Issues_tables, and scripts/Thread_tables to temmplates/Versions_tables_templates, temmplates/Issues_tables_templates, and templates/Threads_tables_templates respectively. The license manager will now recollect licenses after the unusual death of clients (usually related to power failures or other drastic processor halts). Files & issues which have been deleted may be re-introduced without restarting the application or database server. The rz_server will check the write permission on all Info and History files and not start up if they are not writeable by the rz_server process. Modified rz_toolbox to support attribute names with parens in their names. Changed error message generated when users are not allowed to modify an Issue at a selected state. Error conditions generated by RCS will now be expanded in greater detail. Modified the Issues report processing so that display updates won't interfere with report output. Improved user interaction with the rz_install_remotes script to make usage easier. Enahnced rz_install and rz_new_database to allow the user to use ~ and environment params when specifying path names. The file $RAZOR_UNIVERSE_DIR/Names is no longer supported. Its functionality has been replaced by an application specific Xdefaults file. To set the title of an application, a line of the form: Issues*title: Happy Issues*iconName: Silly would set the title bar of issues to be Happy and the icon label to be Silly. For users who would prefer to define their system Xdefaults on an application basis, a file may be placed in $RAZOR_UNIVERSE_DIR with the name Issues, Versions or Threads to apply only to that application. (note, the filename and application name entries must be have their first letter capitilized.) capitilized v3.4(b) Added a new command line (rz_issue_status) and Issues report script (rz_issue_status.rpt) to display brief status of an Issue. Added the command 'razor up' which will simply execute the script $RAZOR_UNIVERSE_DIR/rz_startup The BEFORE scripts can now display a notice with error related information rather than the standard error log text panel. If a file name: /tmp/Razor_notice.<PID>.<Error code> exists, and the <Error code> is non-zero, the contents of that file will be displayed in a notice with a 'Continue' button on it. The <PID> value can be obtained by simply referring to the environment parameter $RAZOR_PID. The <Error code> value is the exit code returned by the script. Added an option to the Uncheckout notice which allows users to put a readonly copy back to the check out directory after completing the uncheckout operation. Added an 'Include file...' menu option to the text panels on the Issue form. This menu is brought up by using the right mouse button in the direct text panel. Added the ability to increment the major version number of files being checked in. The environment parameter RAZOR_INCREMENT_RELEASE is available to BEFORE/AFTER scripts and is set to 1 if the major version number is being incremented, 0 otherwise. NOTE: For those using a VCS script other than those provided for SCCS and RCS, you will need to make modifications to handle the 'ci_bump' command. Added the ability for Issues report scripts to get a file containing the list of Issues selected rather than invoked once for each Issue selected. By adding a third field to the Reports file containing the string "name", the report script will be invoked with the first parameter ($1) specifying a file which has all selected Issues listed and the second parameter ($2) containing the process ID of Issues. Modified rz_issue_summarize_short to include display of the title. Add new script, rz_checked_in_since which will output a list of files which have been checked in since the data/time specified. Corrected rz_mail_issue_catcher script for Solaris platforms. Modified rz_new_database to configure the rz_query and rz_mail_issue_catcher scripts and place them into the $RAZOR_UNIVERSE_DIR/Scripts directory. Corrected bug in Promote in obtaining the selected state. Modified the width setting of LABEL attributes. Enhanced Issues to reuse Issue forms and improve performance. Enhanced Versions to change groups more quickly. Corrected Thread_edit refresh bug which caused by the edit display to become corrupt if another client updated a file in the group being displayed. Modified the definition of the Issues Report dialog so that it will honor Xdefault settings. Corrected the documentation of font setting for the main scrolling lists. The Check-in and Introduce dialogs can now have the default settng for the file control (leave readonly copy, take files, check out for edit) defined through Xdefaults. Terminated branch files will no longer (incorrectly) be included in Thread scripts. The warning/error information presented in Versions during file operations (check in, check out, etc) will now present a list of which files caused the warning/error. Allowed for the definition of the top and vertical widget gap on the Issue form. See the Motif_supplement.ps or Xdefaults.sample for more details. Provided support for the -name option at program startup. This allows multiple invocations of the programs to use different Xdefaults based on the name specified on the command line. Eliminated <CR> from text field input widgets to prevent font warnings. The title of the Browse window icon will now contain the name of the file being browsed. Modified rz_add_group to force the database server to be halted before adding a group. Corrected the 'Compare' dialog in Threads to have the current Thread selected when first displayed. Added a command, 'razor license' for Licenses file updates. Provided for user definition of the Thread script template. If the file Thread_script_template.sh is found in the Tables directory for the Thread group, it will be used rather than the standard template. Please note the the get_file() function must still be defined in the user template in order for the files to be obtained. A sample template can be found in the Razor/scripts/Thread_tables directory and will be placed in new groups as they are created. This template is identical to the template which is written out if no template file is found. For users of the C-shell, a file name Thread_script_template.csh may be used instead. v3.4(a) Modified the rz_install script to honor users who currently use RCS. RCS users can now user single quotes in their title line Operations such as check-in, check-out, get readonly can now be terminated mid stream by selecting Close on the Status or Check-in, Check-out, etc dialogs. The RCS rz_vcs script has been modified to remove files from /tmp to prevent RCS from getting hung up. Titles for check-in should now be properly loaded from the check-out operation. Invalid directories in previous History file entries will no longer cause warnings. The 'Scripts' menu of Versions will not output warnings when selecting 'Cancel' after elements are added, modified, or deleted. The Readonly BEFORE and AFTER scripts are now honored. ======================================== Version 3.4 introduces Razor(TM) to the world of Motif. The functionality provided by this release is based on the current OpenLook version 3.3. There have been no significant changes in functionality although some of the layouts of panels have been modified to take better advantage of those facilities provided by Motif. For those of you running on non-Sun platforms, welcome to Razor! ===> For those running on Sun platforms... The interfaces (Issues, Versions & Threads) are the only things that were changed. Therefore, the existing (3.3(i)) Kid_of_xxx, razor_lm and rz_server programs may be used with either the OpenLook or Motif implementations. Motif provided us the opportunity to give the user greater control over the look and feel of the Razor(TM) programs. Many settings may now be controlled via settings in user .Xdefaults or system wide default files. Examples of the settings along with the defaults used are shown below. One significant change in the product is how the glyphs on the main lists are handled. Now, any number of glyphs can be shown on the main list. Each glyph will represent a different ONE_OF_MANY, ONE_OF_MANY_STACK or STATE attribute value. The Glyphs file has been replaced with a Bitmaps file. The format of the Bitmaps file is a tab separated list of attribute label, attribute value and fullpath to the bitmap to use. The format of each line in the Bitmaps file (located in the Tables directory in the database for each group) will be: <Attr label> <TAB> <Attr value> <TAB> <fullpath to bitmap file> If a value is missing, nothing will be displayed for that value. The definition of relationships between Issues and Versions in now handled through a copy-and-paste operation. Issues are selected from the main Issues scrolling list. Using the right mouse button to pop up a menu from within the Issues scrolling list and selecting "Copy Issues", the Issues will be placed into a paste buffer. Using the right mouse button in the related scrolling list in the Check-in, Check-out, Introduce, Promote, and Introduce panels, you can then select "Paste Issues" to define the relationship. The process of converting from OpenLook to Motif turned out to be a lot more effort than originally anticipated. A great deal of thanks goes out to the Tower Concepts team for their efforts in the development of this version of Razor(TM). It was truly a team effort. Whether it was actual development or covering some of the developers responsibilities, everyone played a significant role. Sun Users - XKeysym Warnings ================================= If you are trying to run the Motif version using the OpenLook Window Manager (OLWM), you will need to modify the $OPENWINHOME/lib/XKeysymDB file as well as make some additions to your .Xdefaults file. To change the XKeysymDB file, you will need assistance from your system administrator. Settings for both files appear below. ! ! OSF Keysyms - append to the file $OPENWINHOME/lib/XKeysymDB ! ! (NOTE: The character '!' is a comment in an .Xdefaults file). ! osfBackSpace :1004FF08 osfInsert :1004FF63 osfDelete :1004FFFF osfCopy :1004FF02 osfCut :1004FF03 osfPaste :1004FF04 osfAddMode :1004FF31 osfPrimaryPaste :1004FF32 osfQuickPaste :1004FF33 osfPageUp :1004FF41 osfPageDown :1004FF42 osfEndLine :1004FF57 osfBeginLine :1004FF58 osfActivate :1004FF44 osfMenuBar :1004FF45 osfClear :1004FF0B osfCancel :1004FF69 osfHelp :1004FF6A osfMenu :1004FF67 osfSelect :1004FF60 osfUndo :1004FF65 osfLeft :1004FF51 osfUp :1004FF52 osfRight :1004FF53 osfDown :1004FF54 ! ! Append this to your .Xdefaults file. ! ! Then, execute the command: ! xrdb ~/.Xdefaults ! ! so that the settings take effect. ! (NOTE: The character '!' is a comment in an .Xdefaults file). ! osfCancel : <Key>Escape osfLeft : <Key>F30 osfUp : <Key>F28 osfRight : <Key>F32 osfDown : <Key>F34 osfEndLine : <Key>R13 osfBeginLine : <Key>F27 osfPageUp : <Key>F29 osfPageDown : <Key>F35 osfBackSpace : <Key>BackSpace osfDelete : <Key>Delete osfInsert : <Key>Insert osfAddMode :Shift <Key>F8 osfHelp : <Key>Help osfMenu : <Key>F4 osfMenuBar : <Key>F10 osfCopy : <Key>F16 osfCut : <Key>F20 osfPaste : <Key>F18 osfUndo : <Key>F14 Controlling the appearance (Xdefaults) ====================================== This is not the proper place to go into great detail about how X translations and actions work. For the discussions here, let us suffice it to say that you can define key combinations on your keyboard to take on behavior which you can control for your own environment. By placing some of the samples below into your $HOME/.Xdefaults file, the various Razor programs can take on your look and feel. The information presented in the paragraphs which follow show you what the current defaults in the system are set to. If you would like to make them something other than what is shown, make the same entry in your $HOME/.Xdefaults file with the new value you would like used. The file $RAZOR_HOME/examples/Xdefaults.sample contains a sample .Xdefaults file which has all of the settings shown in the following paragraphs commented out. To use them, simple include them into your $HOME/.Xdefaults file and remove the comment delimiter (`!'). Foreground and Background Color =============================== The following sets the foreground to black, the background to dodger blue, the menu bar foreground to white and the menu bar background to firebrick for the Issues, Versions and Threads interfaces. Issues*foreground:black Issues*background: dodgerblue Issues*MenuBar*foreground: white Issues*MenuBar*background: firebrick Versions*foreground:black Versions*background: dodgerblue Versions*MenuBar*foreground: white Versions*MenuBar*background: firebrick Threads*foreground:black Threads*background: dodgerblue Threads*MenuBar*foreground: white Threads*MenuBar*background: firebrick Standard Font ============= Several fonts are defined for each of the interfaces. Rather than just throw them all at you in one shot, each will be explained. Each interface has a standard font that will be used if no other font is specified. This is referred to as the StandardFont. It is a helvetica, bold, 12 point font and is defined as fol- lows. Note that Versions also defines a StateFont. This font is used on the Promote panel for the state information. Issues*fontList: -*-helvetica-bold-r-normal--12-*=StandardFont Versions*fontList:\ -*-helvetica-bold-r-normal--12-*=StandardFont,\ -*-courier-bold-r-normal--12-*=StateFont Threads*fontList: -*-helvetica-bold-r-normal--12-*=StandardFont List Font ========= The fonts used by the scrolling lists in each interface are defined as: Issues*XmList.fontList: -*-courier-bold-r-normal--12-*=ListFont Versions*XmList.fontList: -*-courier-bold-r-normal--12-*=ListFont ThreadsThreads*XmList.fontList: -*-courier-bold-r-normal--12-*=ListFont Issue Form Fonts ================ For the main body of an Issue form, both a StateFont and a FormFont are defined. The StateFont is used for the display of the STATE attribute information and is a fixed width font. The FormFont is used for the remainder of the attributes displayed on an Issue form The font used by the two text widgets at the bottom of the Issue form are also fixed width. Take note that the size (width) of this font controls the overall width of an Issue form. Issues*FormWorkArea*fontList:\ -*-helvetica-bold-r-normal--12-*=FormFont,\ -*-courier-bold-r-normal--12-*=StateFont Issues*IssueForm*XmText*fontList: -*-courier-medium-r-normal--12-* Filter Dialog ============= The fonts used by each filter panel is defined as: Issues*FilterForm*fontList: -*-helvetica-bold-r-normal-*-12-* Versions*FilterForm*fontList: -*-helvetica-bold-r-normal--12-* Threads*FilterForm*fontList: -*-helvetica-bold-r-normal-*-12-* Diff Dialog =========== The Diff dialog used by both Versions and Threads defines its fonts as: Versions*Diff*Text.fontList: -*-courier-medium-r-normal--10-* Threads*DiffText.fontList: -*-courier-medium-r-normal--10-* Issue Reports Dialog ==================== The Issues Report dialog defines its font as: Issues*ReportText*fontList: -*-helvetica-bold-r-normal-*-12-* Versions Browse and File Info Dialogs ===================================== The Browse and File Info dialogs define their fonts as: Versions*Browse*Text.fontList: -*-courier-bold-r-normal--12-* Versions*FileInfo*Text.fontList: -*-courier-bold-r-normal--12-* Threads Create Dialog ===================== The Threads Create dialog defines its font as: Threads*CreateForm*fontList: -*-helvetica-bold-r-normal-*-12-* Issue form geometry =================== The height of the work area on the Issue form which contains the configurable attributes is defined as Form.WorkArea. Its height is set and may be changed to meet user preference. Also, the number of rows used by two text widgets at the bottom of the Issue form may also be set. Their settings are defined by default as: Issues*FormWorkArea.height: 500 Issues*SolutionText*rows: 5 Issues*ProblemText*rows: 5 Issues Report Rows and Columns ============================== The number of rows and columns to be displayed for an Issue report is defined as: Issues*ReportText.rows: 40 Issues*ReportText.columns: 80 Issue Form Sashes ================= The position (sashIndent) for the sash on the paned window of the Issue for are defined as follows. A negative number is relative to the right edge, a positive the left. Issues*XmPanedWindow.sashIndent: -30 Word Wrap ========= Word wrap in all text widgets is set to wrap and not scroll horizontally. Issues*XmText.wordWrap: True Issues*XmText.scrollHorizontal: False Versions*XmText.wordWrap: True Versopms*XmText.scrollHorizontal: False Threads*XmText.wordWrap: True Threads*XmText.scrollHorizontal: False Height/Width ============ The height and width of various dialogs is defined as: Issues.MainForm.width: 520 Issues.MainForm.height: 320 Issues*WhichNumber.MainForm.width: 285 Issues*IssueFilter.width: 640 Issues*IssueFilter.height: 500 Versions*Versions.MainForm.width: 660 Versions*Versions.MainForm.height: 450 Versions*Chooser.ChooserMainForm.width: 520 Versions*Introduce*Sw.width: 570 Versions*Introduce*Sw.height: 220 Versions*FileProps*Sw.width: 570 Versions*FileProps*Sw.height: 220 Versions*VersionsFilter*Sw.width: 570 Versions*VersionsFilter*Sw.height: 220 Threads.MainForm.width: 450 Threads.MainForm.height: 300 Threads*ThreadCreate*Sw.height: 130 Threads*ThreadEdit.MainForm.width: 590 Threads*ThreadEdit.MainForm.height: 340 Threads*ThreadFilter.width: 580 Threads*ThreadFilter.height: 350 Threads*BlanketSelections.MainForm.width: 540 Threads*BlanketSelections.MainForm.height: 400 Versions Browse and Script Output dialogs ========================================= The number of rows and columns used for the output of the Browse and Script result dialogs is defined as: Versions*Browse*Text.columns: 80 Versions*Browse*Text.rows: 40 Versions*Script*Text.columns: 80 Versions*Script*Text.rows: 40 Versions Check-in File Control Default Selection ================================================ The check-in dialog allows users to specify the action to take on files which are being checked in. The choices are "Take the files", "Leave a read-only copy", and "Check files back out for edit". The dfault selection can be controlled through one of the following settings: To default to "Take the files": Versions*FileControl.TakeFiles*set: True To default to "Leave a read-only copy" (this is the program default): Versions*FileControl.LeaveReadonly*set: True To default to "Check files back out for edit": Versions*FileControl.CheckOut*set: True Toggle Button Select Color ========================== The color shown when a toggle button is selected is defined as follows: Issues*XmToggleButton.selectColor: Red Versions*XmToggleButton.selectColor: Red Versions*MenuBar*XmToggleButton.selectColor: White Threads*XmToggleButton.selectColor: Red Threads*MenuBar*XmToggleButton.selectColor: White Menu Bar Spacing ================ The spacing between selection on the menu bar for each interface is defined as: Issues*MenuBar.spacing: 10 Versions*MenuBar.spacing: 10 Threads*MenuBar.spacing: 10 Adding more control over text widgets ===================================== Many users prefer that text (and text field) widgets behave in a manner other that the default provided by Motif. What follows is a set of examples of some things that can be set and how this would be done. The action functions shown are pretty much self explanatory. Try them out and pick the ones you like. The examples are shown for the Issues program, but can be applied to Versions, Threads or any other interface. Removing the leading `Issues' from the translation definition will cause the definitions to take effect for ALL text widgets, not just those used by Razor. Issues*XmText.translations: #override\n\ Ctrl<Key>u: delete-to-start-of-line()\n\ Ctrl<Key>e: end-of-line()\n\ Ctrl<Key>a: beginning-of-line()\n\ Ctrl<Key>w: forward-word()\n\ <Key>L6: copy-clipboard()\n\ <Key>L8: paste-clipboard()\n\ <Key>L10: cut-clipboard()\n Q: If I want ^W to be "delete word left of cursor" what would the translation be? Issues*XmText.translations: #override Ctrl<Key>w: delete-word() Q: How would I define <shift>^e to be beginning-of-line. Issues*XmText.translations: #override Shift Ctrl<Key>e: end-of-line()\n\ Q: How do I get the 'delete' key to act like a backspace (destroys the char to the left of the caret)? Issues*XmText.translations:#override <Key>osfDelete: delete-previous-character() Q: How would I get a shifted delete to destroy the char to the right? Issues*XmText.translations: #override Shift<Key>Delete: \ delete-next-character()\n\ Executing commands with keystrokes ================================== It can prove extremely useful to be able to take the output of a command and insert it into a text or text field widget. If text is selected, the text will be replaced by the output of the command. Razor provides this capability through the razor-cmd() action. Placing an entry (or entries) into your $RAZOR_HOME/.Xdefaults file will facilitate this. What follows is an example of how to define the F2 key to place the current date into the widget. Also shown is an example of how to define the F3 key to execute `fmt' on the selected text. *XmText.translations: #override <Key>F2:razor-cmd("echo -n `date +%y/%m/%d`") *XmText.translations: #override <Key>F3: razor-cmd("fmt") Bitmaps ======= As mentioned earlier, the Motif interface allows for multiple bitmaps to be displayed in the main scrolling list of Issues, Versions and Threads. A new configuration file has been added to facilitate the definition of the bitmaps to use. The file is called Bitmaps and resides in the Tables directory with the other configuration files. Please refer to the Razor Programmers Manual for details on database directory layout. A sample Bitmaps file is located in the directory $RAZOR_HOME/scripts/Issues_tables/Bitmaps This Bitmaps contains a list of the bitmaps (glyphs) to use for a specific ONE_OF_MANY, ONE_OF_MANY_STACK or STATE attribute on the main scrolling list for Issues, Versions and Threads. The format of the file is a tab separated list of attribute label, attribute value and fullpath to bitmap in the form: <Attr label> <TAB> <Attr value> <TAB> <fullpath to bitmap> If no bitmap is defined for a particular value, none will be shown and its place will be left blank. The ordering of the bitmaps on each line of the main display will be based on the ordering of the <Attr label> values. The first time a new <Attr label> is found in the list, a place holder for all possible values is allocated. Thus defining the display order. Therefore, the first <Attr label> defined will have its bitmaps appear in column 1. The second new <Attr label> defined will have all of its bitmaps appear in column 2 and so on. Controlling the number of attribute rows ======================================== A new (optional) control parameter has been added to the File_attr_desc file to allow users to specify the number of rows they would like a ONE_OF_MANY, ONE_OF_MANY_STACK, or X_OF_MANY object to be displayed on the various forms (filter, Issue form, introduce, etc). To specify the number of rows, place a <TAB> followed by the desired number of rows at the end of the definition line for the attribute in the File_attr_desc file. If nothing is specified (the default), the number of rows will be computed by limiting each line to a maximum of 6 items.