Re: [hyades-dev] Commiter vote required for M10 check-in

[Joseph P Toomey <jptoomey@xxxxxxxxxx>]

I vote yes.

--Joe

Joe Toomey 
Senior Software Engineer
Rational Software
IBM Software Group

"Antony Miguel" <antony.miguel@xxxxxxxxxxxxx>
Sent by: hyades-dev-admin@xxxxxxxxxxx

05/26/2004 10:36 AM

Please respond to
hyades-dev@xxxxxxxxxxx

To	<hyades-dev@xxxxxxxxxxx>
cc
Subject	Re: [hyades-dev] Commiter vote required for M10 check-in

I vote yes to these changes.
 
Antony
----- Original Message ----- 
From: Dominique
Guilbaud 
To: hyades-dev@xxxxxxxxxxx

Sent: Wednesday, May 26, 2004 3:28 PM
Subject: [hyades-dev] Commiter vote required for
M10 check-in


3 defects to be fixed for M10: 


Defect: 
bugzilla_62467 -- Execution History
model is not incrementally updated during test execution.
Rationale:
This is a fix to have a lost feature apparently loose when we updated the
execution history viewer: the viewer had the capability to be updated every
5s in order to update the current execution history.
Risk Assessment 
No breaking API changes. 
Low risk change. 
Dates 
fix: May 27 
regression test: May 28 (Jerome Gout) 



Defect: 
bugzilla_63682 -- Need a programmatic
way to open the highlighting rectangle from the time compression bar to
the interested lifeline 
Rationale:
This is a fix to have the capability to programatically hightlight an event
in the sequence diagram. This is required for BlueRat for hightlighting
a event (between 2 consecutive messages) when we move the event bar in
the thread view. 
Risk Assessment:
Isolated code changes in three files: 
        org.eclipse.hyades.uml2sd.ui.TimeCompressionBar.java
        org.eclipse.hyades.uml2sd.ui.SDWidget.java
        org.eclipse.hyades.uml2sd.trace.loaders.BaseTraceInteraction.java
No breaking API changes, but a new API is added 
Low risk change. 
Here is a patch containing what we plan to update:

Dates 
fix: as soon as we have the agreement 
regression test: May 28 (Sebastien Veyriere) 



Defect: 
bugzilla_63860 -- Launch Configuration:
Launch Progress Monitor should stop when TEH fails
Rationale:
This is a fix to  avoid infinite "Launching..." jobs in
the Progress view when a Test launch fails because the Test Execution Harness
throws an exception. These jobs never ends, and cannot be cancelled. They
are not blocking, but they are very confusing for the user who might think
the Test is still running. 
Risk Assessment:
No API change. The fix consists in adding a try
{ ... } finally { monitor.done(); }
block around an existing portion of code in AbstractLaunchConfigurationDelegate
class in test.ui. 
Low risk change. 
Dates 
fix: May 27 
regression test: May 28 (Julien canches) 

Thanks

Dominique Guilbaud
Sr. Software Manager
Automated Software Quality
Rational Software
IBM Software Group 
Direct: +33 5 62 16 56 52
Mobile: +33 6 16 47 13 12
dguilbaud@xxxxxxxxxx
ForwardSourceID:NT000158C2