==> DFS COMPONENT NAME:	OT

==> DFS COMPONENT RELEASE NUMBER: 2.2

==> DFS RELEASE TYPE: major

==> DELIVERED BY: uss ON: 13-Dec-01

==> MAIN REASON OF THE DELIVERY: 

     This is the official OT V.2.2 release.

==> DEADLINE FOR DELIVERY TO USERS: 
    
    15-Dec-2001

==> CONFIGURATION REQUIRED FOR INTEGRATION TESTS:

    Standard OT test plan.

==> LIST AND LOCATION OF SPECIFIC TEST DATA TO BE RETRIEVED AND USED FOR
INTEGRATION TESTS: 

    N/A

==> POINTS ALREADY CHECKED DURING UNIT TESTS: TBD

==> POINTS TO BE CAREFULLY CHECKED DURING INTEGRATION TESTS:

    VisiPlots, GUI layout, reports.

==> COMPLETE LIST OF ACTION ITEMS/PROBLEMS REPORTS ADDRESSED BY
    THIS RELEASE:

* Performance of queue loading was much improved.

* Complete GUI redesign: new layout, dialog text, error messages,
  window size, Repository Browser selection and sorting criteria, etc.

* Visiblity Plots report can be generated on selected OBs.

* New check for OBs with missing templates (related reports can be
  generated). 

* An OB's Execution Time is computed and displayed in the Repository
  Browser and the QueueView.

* Extended OB checking capability via External Verification Modules
  (EVMs -- Tcl only). EVMs are also automatically called when adding
  an OB to the execution sequence.

* Centralized Execution Sequence: OBs can be appended to it from
  Queues as well as directly from the the Repository
  Browser. Note that:

  - trying to append an OB with a missing template: error message and
    the OB is NOT attached;

 - trying to append an invalid OB (OB/TSF inconsistency): error
   message and the OB is NOT attached.

  In other words, it's not possible to attach wrong OBs to the
  Execution Sequence.

* Extended reporting capability. "Reports" menu is now accessible from
  several windows.
                 
* Extensive infrastructure changes; robustness of the tool was much
  improved.


==> COMPLETE LIST OF ACTION ITEMS/PROBLEMS REPORTS WHICH ARE NOT
SOLVED YET:

* [1597] In the Repository Browser, Selection Criteria ares: one
  should avoid entering non-numeric characters in the "User ID" and
  "Queue ID" fields. 
  The "Mask ID" field should be avoided altogether.

* In P2PP or OT one may notice the occational stack trace when
  changing user and/or exiting windows.
  The stack trace appears as follows:
  java.lang.NullPointerException
    at javax.swing.KeyboardManager.unregisterMenuBar(KeyboardManager.java:312)
    at javax.swing.JMenuBar.removeNotify(JMenuBar.java:647)
    at java.awt.Container.removeNotify(Container.java:1260)
    at javax.swing.JComponent.removeNotify(JComponent.java:3186)

  This bug is a Swing bug, which was fixed in Jan 1999, available from
  Java 1.2 onwards. It has no effect on the operation of the P2PP or
  OT applications.

* Other OT problem reports: active...
      http://www.eso.org/~uss/ohs/jot/OT-bugs.html
  ...and suspended:
      http://www.eso.org/~uss/ohs/jot/OT-suspended.html


==> LIST AND ISSUE OF UPDATED DOCUMENTS:

    None.	

==> ADDITIONAL COMMENTS:	

    None.

$Id: SEG-RELEASE-NOTES-ot,v 1.14 2001/12/12 09:33:11 amchavan Exp $