Re: [cosmos-dev] Request for respin of i5 candidate build

[Mark D Weitzel <weitzelm@xxxxxxxxxx>]

done. bugzilla updated. 
+1 
_______________________________________________________________________________________________________________
Mark Weitzel | STSM | IBM Software Group | Tivoli | Autonomic Computing
| (919) 543 0625 | weitzelm@xxxxxxxxxx

David Whiteman/Raleigh/IBM@IBMUS
Sent by: cosmos-dev-bounces@xxxxxxxxxxx

08/17/07 03:55 PM

Please respond to
Cosmos Dev <cosmos-dev@xxxxxxxxxxx>

To	Cosmos Dev <cosmos-dev@xxxxxxxxxxx>
cc
Subject	[cosmos-dev] Request for respin of i5 candidate build

Resending this with a better subject to capture attention, per suggestion
from Valentina. :-) 

----- Forwarded by David Whiteman/Raleigh/IBM on 08/17/2007 03:54 PM -----

David Whiteman/Raleigh/IBM@IBMUS
Sent by: cosmos-dev-bounces@xxxxxxxxxxx

08/17/2007 03:05 PM

Please respond to
Cosmos Dev <cosmos-dev@xxxxxxxxxxx>

To	Cosmos Dev <cosmos-dev@xxxxxxxxxxx>
cc
Subject	Re: [cosmos-dev] Candidate build - COSMOS-1.0.0-200708161250

I would like to request approval for defect 200419 (https://bugs.eclipse.org/bugs/show_bug.cgi?id=200419)
to be included in COSMOS i5 build.   Schematron validation is failing
in deployed plugins. 

Including this fix will ensure that all JUnit tests pass, except a couple
very low priority ones.

1. Explain why you believe this is a stop-ship defect. How does the defect
manifest itself, and how will users of COSMOS/ consuming products be affected
if the defect is not fixed?
This is a regression problem that has existed since we started shipping
our plug-ins in jar file format.  The net effect is that Schematron
validation is completely unavailable to the SML-IF validator.

2. Is there a work-around? If so, why do you believe the work-around is
insufficient?
Not really, unless the user wanted to convert the jar file to a directory
structure and also convert the manifest file to a plugin.xml by hand.

3. Is this a regression or API breakage? Explain.
Regression since i3.

4. Does this require new API?
No.

5. Who performed the code review?
To be determined. 

6. Is there a test case attached to the bugzilla record?
No the existing test cases cover this problem.

7. What is the risk associated with this fix?
Low.  Since it just involves a file path character, nothing that was
working before could be affected.  The worst it could do is keep things
working as they were before the rebuild.

8. Is this fix related to any standards that COSMOS adheres to? If so,
who has validated that the fix continues to adhere to the standard?
No. _______________________________________________
cosmos-dev mailing list
cosmos-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cosmos-dev_______________________________________________
cosmos-dev mailing list
cosmos-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cosmos-dev