While we wait to confirm 116700
(both by the bug owners, and for a respin with Chuck's best guess at a fix),
other teams should prepare for their more in-depth testing, be sure test plans
are up to date, API document prepared (not to mention all that facet documentation :)
etc.
Chuck, will you be able to give a quick sanity check to be sure the bug 116700
is fixed in a "built driver", as well as your local fixes? (I had to "unjar" the websphere.core plugin too,
I don't think it was ever meant to be jarred?). The next I-build candidate will be ready about 7 PM (Eastern).
Lastly, I think we are still waiting for confirmation of I-build suitability from Server Team?
(And .. I think Gorkem is "on call" this week for that team?).
Bottom line: I expect I-build to be officially promoted Thursday morning.
We will, though, still begin "lock down" mode ... auto I-builds turned off, I-build only on request, with bugs listed in mail to mailing list.
_______________________________________________ wtp-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/wtp-dev
