WTP 2.0

Ensure all plugin manifests have execution environments specified - David to open bugzilla, each component needs to do this for RC0. This is about half done. Stay tuned for more info.

Move WS bundles to orbit - Goal is end of next week.

Use signed plugin jars - This is not a requirement anymore, but we will still investigate.

Each component must run the eclipse copyright tool to ensure all files have a proper copyright.

Component Leads - Take a look at the new New WTP 2.0 Plan document published by Raghu and make any updates for your component. The purpose is to have a good clear picture of what we achieved and what we wanted to acheive but deferred.

Europa Testing

Components should start setting up Europa update site test environments where they run smoke tests with many projects other than WTP installed, like Mylar, BIRT, etc and make sure WTP function still works.

April 6th - May 18th, WTP RC0

April 2007 - May 2007

Monday

Tuesday

Wednesday

Thursday

Friday

23 Bug Fixing

24 Bug Fixing

25 Bug Fixing

26 Status Call Smoke Test

27 Declare I Build

30 Bug Fixing

01 Bug Fixing

02 Bug Fixing

03 Status Call Smoke Test

04 Declare I Build Platform M7

07 Bug Fixing Start component lead change approval

08 Bug Fixing

09 Bug Fixing

10 Status Call Smoke Test

11 Declare I Build EMF M7 produce test candidate

14 Function and Compatibility Tests

15 Defect Verifications Mustfix defects

16 Defect Verifications Mustfix defects

17 Defect Verifications Status Call Thumbs Up Test

18 Declare WTP 2.0 RC0

Build Status

Please smoke test and update wiki to declare RCO I Build.

JUnits?

Component Leads: please update the exception section of WTP_2.0_Ramp_down_Plan_for_Europa with the relevant info and bugzilla numbers for exceptions to M6 feature complete.

API Violations Review - David

Background

The belief is the platform is solid and there is no need to fix, but in reality, when we move to the 3.4 base, that's when the platform is likely to make internal changes. So if we have internal dependencies, we may be broken out of the gate and lose time in M1. Also, make sure your plugin ranges are correct.

Action 1 = For any violation, open a bug to request API or fix code to not use internal discouraged access. An example is using images or labels from other plugins, these should be copied into your plugin. Also, using internal classes instead of the API interfaces.

Action 2 = If you do have a clean plugin of API violations/discourage access, switch prereq ranges wide so you can react to small version number changes without issue.

Action 3 = To be able to develop with discouraged access enabled, we need to update plugin's .classpath rules. Should we turn off defaults to expose all warnings to get a quicker resolution?

Performance Tests

Assign component lead ownership to the specific test suites.

By ownership, you are responsible for sanity checking the current suite of tests, ensuring they are proper in timeliness and acuracy, and then making sure each week there are no regressions and that they are still running properly.

I still need to update the M6 results. But you can run your tests locally or look at the M5 numbers for reference.

Performance Test Owners

wst-common - Konstantin

wst-css - Nitin

wst-html - Nitin

wst-server - Tim

wst-wsdl - Valentin

wst-xml - Nitin

wst-xsd - Valentin

jst-j2ee - Carl

jst-jsp - Nitin

jst-server-tomcat - Tim

jst-ws - Kathy

jst-jsf - Raghu - to be added later

jpa - Neil - to be added later

Known Issues

Switch the 2.0 performance tests baseline to be the latest 1.5.x

The XSD and WSDL tests are not running. Adding them causes the suite to hang. Needs investigation.

The baseline test needs to be rerun each week to eliminate false "hiccups" in performance.

Action Items

Improve the UI readability and cohesiveness of the output result pages

Improve the actual tests. Why do some take so long? Why do some results fluctuate? Why do some have 160% performance degradations? Are the tests even still valid?

Allow committers to reliably and efficiently run perfomance suites in the workspace before checking in code