Glossary Contact us Log in
Search
 
Lucent Technologies, Bell Labs Innovations
*
Systems Technology Center Home
Sablime® Configuration Management System
Product Info
Downloads
Documentation
Ordering Information
Support
Lucent® nmake Product Builder
Lucent® Exptools
STC Services
Contact Us
*
v61, Update 2 - Expected Contents
Update 2 of v6.1 will provide a sizable set of small fixes and enhancements in a timely fashion, rather than concentrating on major features. These fixes and enhancements are intended to improve the user experience and eliminate some annoyances. No splashy new features, but solid improvements.
V61u2 should be released sometime in May.

Enhancements

  • Remove "ofile" from Web report command
    The "ofile" field only permits the output file to be specified on the host. Usage is not intuitive from the Web (where users should simply do "Save As..." after producing their report. Remove the field from the Web view to the report command. (sab060036)

  • Build "mk_approve" enhancements into approve and testpass
    Enhances approve and testpass so that they break the MR approval list into smaller, dependent sets, before approving them. This greatly lowers the risk of encountering a failure due to overly long inclusion lists in the "s." files, and lessens the liklihood of corruption if an approve operation is interrrupted. (sab060033)

  • Extend MR-selection-by-state to sget and mk_approve. Add "closed" as state.
    Sablime v60u2 added state names (including such things as "submitted+") to the way MRs can be specified in getversion. This change brings those enhancements to sget and mk_approve. It also gives sget and getversion the ability to specify "closed" MRs, and "approved+" which means "approved, closed". (sab060030,1)

  • Improve performance of Web Accept command
    This MR allows the Web Sablime accept command to build the menu of candidate MRs quicker, especially for databases with a huge number of such MRs. (sab060026).

  • Provide custom report facility
    Provide a facility so that users can create their own report scripts or programs, and have these be available from a Web Sablime menu. (sab060017)

  • Add access to all commands to the lifecycle interface.
    This MR updates the graphics and layout of the lifecycle interface main page, and includes an "Other Commands" selector so that non-lifecycle commands can be selected. (sab060014)

  • Add fcreate to Concept segment of lifecycle
    This adds a link to the fcreate command to the concept segment of the lifecycle interface. Although fcreate is typically used by a developer to create/accept/assign to him/herself, it also can be used by an Admin to create/accept/assign to someone else. (sab060000)

  • Have "Composite" or "Tabbed" MR Details view persist
    This enhancement allows the user's choice of "Composite" or "Tabbed" view on the MR Details page to be retained from session to session. (sab050108)

  • Permit ownership of groups by groups
    Except for permitting groups to be owned by themselves, Sablime doesn't permit groups to be owned by other groups. This change allows any group to be owned by a PTS ID group, thereby allowing any member of the second group to update the first.
    An obvious use for this is to allow a group of people to update the MR group that is used for builds. (sab050088)

  • Make MRGUDF1-5 available to more commands.
    Customers want to use MRG User Defined Fields for data items that would be set before an MR is submitted. This MR makes those fields available (but, by default, still hidden) on the accept, assign, fcreate, reject, and testpass commands. (sab050086)

  • Allow "unedput" to leave file checked out.
    Traditionally, unedput has left the file in a non-checked-out state, so you can proceed to unedput multiple changes one by one. This MR adds a "Leave Files Checked Out" option, so that you can use unedput as a true undo of an edput, leaving you with a checked-out and writable file - as if the latest edput had not been done at all. (sab050068)

  • Add file view capability for Binary Files
    This MR adds a "View" button in Web Sablime File Browser for files stored in SBCS (i.e. files stored as binary). If the file can be displayed in the browser, it will be, otherwise it will be handed to the local OS for display by whatever application is appropriate. (sab050061)

  • Have Directory Browse button start at same place as previous Browse
    This MR causes the Web Sablime directory Browse function to start at the same location that was most recently selected. If the user chooses a different "drive", then it starts at the most recently selected directory on that drive. (sab040181)


  • Fixed Bugs

  • Sget complains about self-populated value
    Fixes a condition where sget would change the value in the directory Browse widget from, for example, C: to C:\ at run time, but complain if you inserted or re-used that value yourself. (sab060041)

  • Getversion of snapshot should not create writable files.
    Fixes a condition - made more common by the addition of an unrelated feature of the initial release of v6.1 - where getversion of a snapshot can create writable files, causing subsequent getversions to fail. (sab060040)

  • Inconsistent handling of comment delimiter
    Console Sablime replaced the "tilde" in a menu item comment with a space; while Web Sablime displayed the "tilde" and added a space. In either case, if the value itself included a space, it was unclear where the value stops and the comment starts. This MR causes all menus to display the value unaltered (including the comment delimiter). (sab060035)

  • Wsabcheck assumes config file is in "conf"
    This MR fixes wsabcheck (and a couple other places) where the configurable location of the conf files themselves was not being respected. (sab060029)

  • Getversion consumes excessive memory
    Repairs a condition where - even with a modest database size and a generous amount of physical memory - getversion could exhust the available memory and then fail. (sab060027)

  • Improper handling of apostrophe in abstract
    Fixes a bug where an apostrophe in an MR abstract (or certain other textual fields) was unnecessarilly quoted and protected by a backslash. (sab060020)

  • Missing description file causes report command to mis-report other items
    Fixes a bug where the report command - once it noticed an MR's Description file was missing - would fail to report the existence of other items such as the History file or Resolution file. (sab060019)

  • Directory listing not sorted in Browse widget
    In the Addsrc and Edput commands, when you use the "Browse" widget to navigate to a network drive, the drive's contents are not presented in any logical order. This MR will cause the contents to be sorted alphabetically. (sab060015)

  • wsabcheck complains after a fresh install
    If you run wsabcheck immediately after installing Sablime, it will report that a couple files have incorrect permissions. (sab060008)

  • Cannot addsrc a file named "0" from the web
    The web addsrc command doesn't properly handle a file named simply "0" (as in "zero"). (sab050102)

  • Commit fails (silently) without /bin/diff
    The commit command (modify function) expects to use /bin/diff, but if that's not available it proceeds without reporting an error and without updating the commit file. (sab050078)

  • Web source commands fail if directory name has leading or trailing spaces
    If a user supplies such a directory name to the Web Sablime source commands, the commands fail with a Java error. This MR will cause Sablime to ignore leading or trailing white space (including white space adjacent to a directory delimiter). If the user really wants these, then they can quote the entire string. (sab050023)

  • Study and Propose list some invalid MRs
    The Web Sablime MR menu for these command will sometimes include MRs that are not valid for all the selected generics. (sab050000)

  •  
    Terms of use    Privacy statement   
    Copyright © 2006 Lucent Technologies. All rights reserved.