[wtp-releng] J2EE smoke retest passes] Status: M200601251151 is current

[John Lanuti <jlanuti@xxxxxxxxxx>]

J2EE smoke test now passes on M200601251151.
 Blocking defect fixes verified.

Thanks,

John Lanuti
Software Engineer, IBM Rational
jlanuti@xxxxxxxxxx
t/l 441-7861

"I know this lady way down in my country.
She is so pretty that my eyes throw disguises at me.
Now we will sit and we'll wonder about our future,
But now I'm thinking that today sounds fine to me."  - Of A Revolution

David M Williams/Raleigh/IBM@IBMUS
Sent by: wtp-releng-bounces@xxxxxxxxxxx

01/25/2006 09:59 AM

Please respond to
Webtools releng discussion list <wtp-releng@xxxxxxxxxxx>

To	Webtools releng discussion list <wtp-releng@xxxxxxxxxxx>
cc
Subject	Re: [wtp-releng] Status: M200601251151 is current weekly        M-build        candidate ... but .... a little more needed.

Thanks John. 

ok, that narrows it down to 
org.eclipse.wst.common.project.facet.ui 
I think for 
[120201] Fixed facets and categories don't mix 
which is listed as "normal", but a comment says "should
be on hot list"? 

So, remaining actions are 

successful J2EE (re) smoke test 
successful Server Team smoke test 
successful Facets Smoke test (and confirmation that 120201 is what was
drove re-release). 

= = = = = = = = = = = = = = = = = = = = = 

Oh, and John and Naci and Gorkim .. would be good when we find a regression,
as for the 
failing J2EE Smoke test to devise a JUnit test that fails on old version,
succeeds on new version. 
I don't mean to pick on you, but in general this is a "best practice"
our WTP project needs more 
discipline on. On the one hand its easy to think the "code owner"
should provide it, on the 
other, since its obviously important to J2EE smoke tests, there's no reason
the client (J2EE team) can 
not provide it since they are well motivated to be sure it doesn't happen
again. 

thanks all.

John Lanuti/Raleigh/IBM@IBMUS
Sent by: wtp-releng-bounces@xxxxxxxxxxx

01/25/2006 09:34 AM

Please respond to
Webtools releng discussion list <wtp-releng@xxxxxxxxxxx>

To	Webtools releng discussion list <wtp-releng@xxxxxxxxxxx>
cc
Subject	Re: [wtp-releng] Status: M200601251151 is current weekly M-build        candidate ... but .... a little more needed.

Naci put in a fix for https://bugs.eclipse.org/bugs/show_bug.cgi?id=124146
in the annotations plugin.  This
was opened last week as inhibiting our smoke test and he made and tested
the fix in 1.5 but forgot to release to 1.0.1.   I can test it when
I test the server fix. 

I also revised a fix in j2ee.core which needed to be reverted because it
changed a protected internal API which extenders were actually using.  This
was for 123308.  The old API now just calls the new one, so it has
already been tested, just not a breaking change anymore.

Hope that helps, 

John Lanuti
Software Engineer, IBM Rational
jlanuti@xxxxxxxxxx
t/l 441-7861

"I know this lady way down in my country.
She is so pretty that my eyes throw disguises at me.
Now we will sit and we'll wonder about our future,
But now I'm thinking that today sounds fine to me."  - Of A Revolution

David M Williams/Raleigh/IBM@IBMUS
Sent by: wtp-releng-bounces@xxxxxxxxxxx

01/25/2006 09:20 AM

Please respond to
Webtools releng discussion list <wtp-releng@xxxxxxxxxxx>

To	wtp-releng@xxxxxxxxxxx
cc
Subject	[wtp-releng] Status: M200601251151 is current weekly M-build candidate ... but .... a little more needed.

There's been 4 changes. Only one of which I know about.  Can others
please list the blocking/critical defects of why the other three plugin's
changed, and recommend re-test actions? 

I'm sure 

plugin@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx=v20060125_0800,:pserver:anonymous@xxxxxxxxxxxxxxx:/cvsroot/webtools,,jst/components/server/plugins/org.eclipse.jst.server.generic.core

was for 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=125032
and while I've re-opened that bug asking for clarification and follow on
actions, it should no longer be blocking and ready for John to re-test.


These were the other three plugins that changed: 

plugin@xxxxxxxxxxxxxxxxxxxxxxxx.annotations.xdoclet=v20060124_1017,:pserver:anonymous@xxxxxxxxxxxxxxx:/cvsroot/webtools,,jst/components/ejb/plugins/org.eclipse.jst.j2ee.ejb.annotations.xdoclet
plugin@xxxxxxxxxxxxxxxxxxxxxxxxx=v20060124_1711,:pserver:anonymous@xxxxxxxxxxxxxxx:/cvsroot/webtools,,jst/components/j2ee/plugins/org.eclipse.jst.j2ee.core
plugin@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx=v20060124_1729PST,:pserver:anonymous@xxxxxxxxxxxxxxx:/cvsroot/webtools,,wst/components/common/plugins/org.eclipse.wst.common.project.facet.ui

Can the responsible parties please document what changed (or, at least
document bug number here) and what re-test actions needed. If any. 


Plus, I think we are still waiting to hear "pass/fail" from server
team? _______________________________________________
wtp-releng mailing list
wtp-releng@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-releng
_______________________________________________
wtp-releng mailing list
wtp-releng@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-releng
_______________________________________________
wtp-releng mailing list
wtp-releng@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-releng