Community outreach Bug Day. Teams wishing to participate should sign up at this month's wiki page by the 26th.

Nitin is contact for JST and WST for first bug day and will post an announce to the newsgroup. Other committers should join as well. A key activity will be triaging bugs, i.e. making sure a bug has enough information to reproduce and possibly to attach a patch.

This is a great chance for WTP to start doing a better job of engaging and interacting with the open source community.

Let's review the submitted features and logged enhancement requests in bugzilla as updated in the requirements document for this release.

August 7th - (Delayed one week) We will sign off on component lead and committer input and take forward for community review.

Performance Tests

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

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

Web Service tests still do not present results.

There is a test which is hanging and needs to be manually killed. Believe it is the ValidateOAGISXSDTestcase. Opened 197862.

Graph only plots current results, not baseline results.

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 performance suites in the workspace before checking in code

M1

M1 Schedule?

July 2007 - August 2007

Monday

Tuesday

Wednesday

Thursday

Friday

23 Planning

24 Planning

25 Planning

26 Status Call

27

30 Planning

31 Planning

01 Planning

02 Status Call

03

06 Planning

07 Planning

08 Planning

09 Status Call

10

13 Development

14 Development

15 Development

16 Status Call Smoke Test?

17 Declare I Build? Platform M1?

20 Development Start component lead change approval

21 Development

22 Development

23 Status Call Smoke Test

24 Declare I Build EMF M1? Write tests and produce FVT driver

27 FVT and Compatibility Tests

28 Defect Verifications Mustfix defects

29 Defect Verifications Mustfix defects

30 Defect Verifications Status Call Thumbs Up Test

31 Declare WTP 3.0 M1?

There will be some code work just to declare M1 as functional. For example, the platform has removed the tomcat plug-in and there are other plug-in prerequisite version ranges which will need to be updated.

M1 Themes - Each milestone we will have general, cross project themes. Open to suggestions like performance, accessibility, adopter readiness, etc.

Evaluate non-API use and ensure requests are open if our code cannot be changed.

Web Services Component Team

Java EE Component Team

Dali JPT

JSF

releng

API Violations Review

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?

References

Instructions for tagging existing and new WTP wiki pages can be found at WTP's Category page; remember, we can create subcategories as well