Release notes December 2005

Transcription

1 Sablime v6.1 Update 1 Release notes December 2005 Revised 17Apr2006 Updated URL s to reflect new layout of Sablime product web site. Update 1 of Sablime v6.1 for UNIX* / Linux* is a non-database affecting update to Sablime v6.1, and includes the new File Attachments feature, a couple of other significant enhancements, and the usual collection of small enhancements and bug fixes. File Attachments Update 1 of Sablime v6.1 provides the ability to attach files to Sablime MRs. When you create an MR, you can attach a screenshot showing the problem. When you propose a solution, you can attach a Word document with detailed requirements. Places in Sablime where you normally supply a block of text, you can now attach one or more files. See Using the File Attachment Feature for more details. Batch_addsrc Update 1 adds a new command on the host side called batch_addsrc. This is the similar to primsdb because it permits adding many files at once. Batch_addsrc like addsrc on Web Sablime lets you add files from local copies, even when the files already exist in another generic. See Adding Many Files to a Generic for more details. MyMRs Customizations With Update 1, you ll be able to select which database fields you want to have displayed on your MyMRs table. See Using the MyMRs Report for more details. Note: If you are upgrading from pre-v6.1 versions of Sablime, you may wish to review the Release Notes for other intervening releases in order to understand the impact on your existing system. This document describes those changes that are part of the upgrade from v6.1 to.

2 Miscellaneous Enhancements and Bug Fixes Web install: Script now correctly specifies /bin/ksh instead of /bin/sh. Addsrc and Edput: Now handle file names with dollar signs better. Depend: Now works with closed and approved MRs. Newgen: Eliminated meaningless ( Is this a released generic? ) question. MyMRs: Now shows the MRs test-assigned to a group of which you re a member. Initsab: Simplified, with several unnecessary questions removed. Newgen: Now creates proper group names when the generic name is extra long. Mrgedit: Second screen values no longer get replaced by defaults in noprompt mode. Hotline.ck: No longer reports wrong error when directory name contains spaces. Getversion: Snapshots with files with spaces in names now extracted properly. Mrnote: Like create and report, mrnote no longer requires a license. Addsrc, Edget, Edput, Getversion, Setnode, Sget, Unedput: Target Directory field widened so that longer paths are visible. Web Source commands: Added code to prevent an overly restrictive umask on the host from causing file uploads to fail. Web Source Browser: View Changes function now handles file names with dollar signs. Acquiring Sablime v6.1 Update 1 Instructions for downloading and installing Sablime v6.1, Update 1 are available on the Sablime web site. The Sablime Installation Guide is for first time installers of Sablime, while the Sablime Upgrade Guide is for Sablime users upgrading to from an earlier version. You can upgrade from Sablime v5.0 or later directly to. Your existing license file will continue to work. Support for Earlier Releases Support is provided for the current and previous major releases of Sablime. With the release of v6.1, that means that v6.1 and v6.0 (all updates) are supported. Sablime v5.2, released over 5 years ago and last updated in 2001, is now unsupported. Documentation Sablime includes a completely new Usage Guide. The Usage Guide is intended to be a more focused and user centered document for all phases of Sablime usage. The Usage Guide is updated for the new Update 1 features. The three traditional Sablime documentation manuals will remain available during this transition time. These are the User's Guide, the Administrator's Guide, and the User's Reference Manual. These have not been updated with information regarding File Attachments or other Update 1 features. Release Notes 2 December 2005

3 The 3 traditional manuals are included in the Sablime distribution, and are also available on our web site. The Usage Guide is available on the web site along with these other Guides : Sablime Installation Guide Sablime Upgrade Guide Sablime Web Installation and Upgrade Guide Sablime Web Security Guide Sablime Getting Started Guide Sablime Visual Studio Plug-in Guide Sablime Eclipse* Plug-in Guide Feedback / Helpdesk The Sablime team welcomes feedback. Please contact us at sablime@lucent.com. This is also the address of Sablime s helpdesk. Mailing List If you are not already a member of the Sablime Announcements mailing list, you can subscribe by sending to listserv@lucent.com, with subscribe sablime-announce <your_name> in the body of the . To unsubscribe include signoff sablime-announce as the body. Release Notes 3 December 2005

4 Supported Platforms Sablime runs on the many common UNIX platforms, and on Linux. Web clients can be those machines or on Windows* platforms. If you want to use a Windows OS machine as the Sablime host, you can use Sablime for Windows (sfw1.1). The Visual Studio plug-in and the Eclipse plug-in supplied with the v6.1 release will work with either a v6.1 Sablime host or an sfw1.1 host. Machine OS & Version HP-UX hppa10 HP-UX (1) Solaris* Solaris 2.6 sparc5 Solaris 2.7 Solaris 2.8 Solaris 2.9 hppa11 HP-UX 11.x rs6k AIX4.3 rs6k_5 AIX5.1 Red Hat * 7.2 Red Hat 7.3 ilinux Red Hat 8.0 Red Hat 9.0 Windows NT * Windows 95 Windows 98 Windows 2000 Windows XP Sablime Host Binaries? Yes No (See sfw1.1 for Windowshosted version of Sablime) Netscape, Mozilla series with Java * plug-in: Minimum Version Netscape 7.0 Mozilla (2) Internet Explorer with Java support: minimum version No 5.0 (3) Java JRE minimum version for smerge on client machine No 1.2 OS Releases displayed in boldface are the build platform for that architecture 1) HP-UX NIS+ systems relying on the nsswitch.conf facility to determine the Name Service are not supported. 2) Netscape 7 and Mozilla browsers were tested on sparc5, ilinux and Windows. The browsers may be available for other platforms in binary or source form and should work with Sablime. Firefox and other standards compliant browsers should be usable also. 3) For improved security, Internet Explorer 5.5 is the recommended minimum. Pricing and Licensing x General licensing information is available on the Sablime web site. Price quotes are available from the Customer Care team at software@lucent.com. * UNIX is a registered trademark of The Open Group. * Linux is a registered trademark of Linus Torvalds. * Eclipse is a trademark of Eclipse Foundation, Inc. Release Notes 4 December 2005

5 * Java and Solaris are trademarks or registered trademarks of Sun Microsystems Inc. in the U.S. and other countries. * Red Hat is a registered trademark of Red Hat Software Inc. * Windows, Windows NT, and Visual Studio are trademarks or registered trademarks of Microsoft Corporation in the United States and other countries. x Sablime is a registered trademark of Lucent Technologies. Contents copyright 2005 Lucent Technologies. Permission to photocopy in support of a licensed installation of Sablime is hereby granted. Release Notes 5 December 2005

6 Using the File Attachment Feature Command File Component Each of the Sablime commands listed on the left include a text file component. The create Description contents of these files must be simple ASCII fcreate Description text. propose spawnmr submit reject testpass Solution Spawn Notes Resolution Rejection File Test Notes However, when using Sablime s Web interface, you can attach one of more files to these file components. The attachment can be any type of file, including binary files such as bitmap files, or Word documents, etc. Sablime stores the attachment with the database, and the file can be extracted and viewed by other Web Sablime users. The Add Attachments: control is usually directly below the text box for entering the text file component. Sablime does no analysis of the attachment, nor does it do versioning of the attachment. It simply permits the file(s) to be attached and removed by the appropriate users.once you ve added one or more attachments, a table will appear showing their name(s). The Action selector lets you remove the attachment. Similarly, on the MR Details page, if one of the displayed file components has an attachment, a table like the one above will appear, with the option to replace or remove the attachments. The permissions for adding or removing attachments are the same as for the associated file component. For example, just as anyone can use mrnote to append to the description file of an MR, anyone can add an attachment. Only the MR Administrator can remove the attachment. Attachment Names and Directories If you add an attachment that has the same name as existing attachment to that file component, Sablime will attach the new file as filename_#, where # is a number (1, 2, etc). This only applies if the same-named attachment was already stored in Sablime. You cannot add two files of the same name during the same session. Note that the attachment s location (i.e. folder or directory) is not recorded by Sablime. When you retrieve an attachment, it is placed into the folder/directory you select on the local machine. [Return to Release Notes] Limiting Size and Number of Attachments Sablime administrators can limit the size of the attachments by setting the MAXATTSIZE variable in wsab.conf as part of Web Sablime configuration. Administrators can also set a limit for the number of attachments per file component with MAXATTNUM.

7 Adding many files to a generic The addsrc command is typically used for adding files to a generic. Addsrc adds files to one directory at a time, and this is usually good enough for day-to-day use. Occasionally - at the beginning of a new release, or to incorporate a new set of files from a 3 rd party, for example - you might want to add a large number of files. The batch_addsrc command is intended for such cases. The batch_addsrc command is only available on the Console interface to Sablime (that is, it is not available through the web browser). Batch_addsrc displays a note telling you what it is going to do, and then uses a prompt and response interface to gather the following information: MR Number One MR Number An MR currently assigned to you in the current default generic. List of Files to Add The full path to a file. This file should list one directory/file item per line. The directory component should be a directory of your project s node structure. An entry of src/lib/get_data.c would cause the file get_data.c to be added to the directory src/lib. Add from Local Copies or from a Previous Generic? Use Local Copies or Previous Generic Like the web addsrc, batch_addsrc can add files from local copies of the files (even if the file is already in Sablime), or can copy the contents from an old generic. It cannot do both at once, though. The following questions are only asked if you answered Use Local Copies above. Node Root - A full path on the local system This is the node on the local system where all the files listed in List of Files to Add can be found. Do you want to use the extension for the file type? y or n You can allow batch_addsrc to determine the file types by looking at the files extension. This is based on the FileExtMap file in your command bin. For files that are already in Sablime, this will be ignored, and the existing file type will be used. Store as Binary? y or n For files that are new to Sablime, do you want to force Sablime to treat them as binary files? You should only do this in special circumstances when, for example, the files qualify as non-binary but need to be handled as binary anyway. See the Binary Files box on the addsrc page for more information. For files that already exist in Sablime, this value will be ignored, and the existing treatment be used. The following questions are only asked if you answered Previous Generic above. Previous Generic One generic name Enter the name of the generic from which to copy the files. Should the files be made Common? y or n Answer y if you want the file to be common between the current generic and the Previous Generic. When files are common, and an MR is assigned to you as developer in both generics, you only need to change the file once, and the change will be applied in both generics. Non-common files change independently in the generics. If you answer y to Common, then the most recent version from the mr Branch

8 of the Previous Generic is automatically used. The following questions are only asked if you answered n to Common Branch ofc or mr This specifies the base branch. The ofc branch has all approved changes made to this file. The mr branch contains all changes, period. If you want the latest version, select mr. If you want to selectively apply unapproved MRs, select ofc, and then add MR Numbers. See the chart below for all the possibilities. MRs for Specifying Version - An MR group. Default is empty Enter the names of an MR group in the current generic. Changes made by these MRs will be included in the added files. This won t cause more files to be added, just more changes to the specified files. If you re adding the latest version, you d leave this empty. Include Missing Depended Upon MRs? y or n Do you want addsrc to automatically include the changes from any MR that one of your MRs for Specifying Version depends on? The command will fail there are missing depended-on MRs and the selection is n. Usage Notes Batch_addsrc brings forward the same setting for File Owner that existed in the previous generic. For new files, it leaves File Owner unset. Even though files exist and can be changed independently within each generic (depending on their common status), the file s name must be unique within its directory across all generics. The batch_addsrc command can be used by anyone with a PTS ID and an Assigned MR. In addition, the Source Administrator (SA) may use addsrc even if the MR is not assigned to her/him. Addsrc doesn t send and the Command Permissions feature isn t usable for addsrc, for execution permissions or for delivery. Addsrc result variations based on branch selection Branch MR Numbers Result ofc None Specified All approved changes 1. Specified 2 All approved changes 1 plus changes made by the MRs. mr None specified All changes (i.e. latest version) Specified Initial version 3 plus changes made by the MRs. 1 If a file without any approved changes is chosen, the result will be an empty file. When ofc is selected, only non-approved MRs may be in MRs for Specifying Version 3 Initial version is the file as it was when it was added to the Previous Generic Note: The traditional Sablime commands for adding individual files - addisrc and addgsrc still exist and can still be used from the Console interface. Likewise the traditional command for adding many files primsdb still exists. See the earlier versions of the system documentation for full descriptions of these commands. [ Return to Release Notes ] Release Notes 8 December 2005

9 Using the MyMRs Report What MRs are assigned to me? When are they due? Am I supposed to be studying some MRs too? Sablime provides a simple facility for answering those types of concerns. Called from either the Lifecycle or the Classic interface, the MyMRs report shows a table listing the MRs that are currently assigned to you for study, development, and test. You can get this report by pressing the MyMRs button on the Classic interface, or by pressing the MyMRs hyperlink in the development segment of the Lifecycle interface. The MyMRs links in the other segments list different sets of MRs, listing the MRs in the early created and understudy states in the Concept segment, for example. You can use the checkboxes to select or unselect individual MRs or use the Select/Unselect All buttons to choose a set of MRs, and then save that set as a MR group. The group name can then be used in place of individual MR names or lists in other commands. Each MR Number on the list is a hyperlink to the MR Details page for that MR. From the MR Details page, you can do MR operations such as checking out files, submitting the MR, etc., and you can see the MR history, dependencies, and status within each generic where the MR appears. MR Details

10 Using the settings button from either the Lifecycle or Classic interface, you can change which tables and which generics to display. Furthermore, you can choose which information you want to display within each table: Because the MR Number and Generic are the keys for all the remaining data, you cannot remove those fields from the tables. If you make no selections in the My MRs settings page, the default report layout (see previous page) is used. Don t forget to scroll down and press Apply after making changes. I still don t see all My MRs! The MyMRs tables show the MRs that are ready to be worked on. If you re listed as developer on an MR, but the MR is not in the assigned state, then it will not show on the list. Similarly, if an MR is assigned to you for testing, but isn t in the appropriate state to do the testing, it won t be listed. You can use the Browse MRs Facility to get the full list of MRs assigned to you, or to get any number of other MR-based lists. [ Return to Release Notes ] Release Notes 10 December 2005