WTP 2008-03-27

WTP Development Status Meeting 2008-03-27

Attendees

Project Leads
Konstantin	Y
Tim	Y
Nitin	Y
Kathy	Y
Chuck	N
Naci	N
Raghu	Y
Neil	Y
David	Y
Helen	Y
Philippe	N

Committers
Bob	Y
Carl	Y
Dave	N
Phil	N
Kaloyan	Y
Larry	N
Amy	N
Kate	Y
Angel	Y
Rob	N
Brad	Y
Valentin	N

Friends
Nick	Y

Announcements And Reports

Several teams announced version increments/API changes in this weeks I build, please update the New Help for Old Friends III page with the changes
P2 adoption almost complete. Build is fine, still have Junit issues.
Rob Frost leaving, thanks for all your hard work! Rob's work will be transitioned to Chuck's team.

Minutes:

David: will try a build with p2 disabled to verify Junit issues. Will be ready in 4-5 hours.

Please do some preliminary tests with the 03270100 platform build, but no offical smoketest till that build is done

Konstantin: compatibility to the platform team

David:will pass along issues with forward

EclipseCon feedback

Kathy: tutorials uploaded on the key was very useful for setup

Bob: having tutorials was good

David: committers BOF was fun and informative, will send out a note to wtp-dev, pls send me any other feedback you have

Focus on Backlog and Quality metrics (Neil)

Current Focus Item

Untargeted bugs with patches attached opened before January 1st, 2008 (Last week - 24; Currently ~ 23)

Options are

Target bug for a release or "future"
Mark as Invalid or Wont Fix

Upcoming Focus Item

Past Focus Items

Untargeted Enhancements opened before January 1st, 2007 (Last week - 62; Currently ~ 58)

Before July 1st, 2007 - 109
Options are

Invalid - Enhancement does not fit with the scope of the project or is already implemented.
helpwanted keyword - This is a valid request, but due to committer resources and other priorities, outside help will be needed to make this happen.
Future - I would use this in conjunction with the helpwanted keyword. I use this for legitimate requests that are important but will not make any planned release, but likely will make a future release.

Untargeted severity "Major" and higher bugs opened before January 1st, 2007 (Last week - 2; Currently ~ 0)

Before July 1st, 2007 - 21

Where did they all go?

Minutes:

Neil: will focus on untargeted enhancements again after M7

Focus on Requirements Planning (Raghu)

Review and Update the WTP 3.0 Plan by April 7

Projects with no committed items: none

Please update status page

Please review untriaged enhancement requests

Untriaged Enhancement Requests ()

Plan items in Bugzilla ()

Reminder: Any feature work that slips past M6 needs PMC review, and needs to be explicitly listed on ramp down page. (Before the end of M6!)

David will update docs and send reminder note.

Document updated to clarify policy. See WTP 3.0 Ramp down Plan for Ganymede

Post WTP 2.0.2

New patches are ready and sent for test => 222531

Recommend teams use update manager, and adding the "webtools/testUpdates" site, or use a policy file, as described at end of WTP Patches for Release 2.0.2

May have issues with install when the previous patch has already been installed, currently assessing

Currently 1 known "bad bugs" (critical, major, hotbugs) to be included in an offical post 202 patch

222531

Patch creation instructions
Smoketest

Minutes:

Smoketest is good, but have issues with updating if the previous patch is installed. Will need more investigation.

WTP 3.0 M6

our +2 date: Monday, April 7 2008
Final Code released by March 28th

Plan 02/18 - 02/22

Development 02/25 - 03/28

Test 03/31 - 04/04

WTP 3.0 Ramp down Plan for Ganymede

M6: API, feature, UI freeze

Any issues with API/feature/UI freeze by Friday?
It's New and Noteworthy time, see Nitin's email from the 10th

WTP_Functional_Test_R30_M6

Builds

Build Breakages Board

3.0 Smoketest results

Bug Lists

3.0 Invalid Targeted Bugs (~3)

3.0 M6 Targeted Bugzilla Enhancements (~16)

All Remaining 3.0 Targeted Enhancements (~123)

3.0 M6 Remaining Targeted Bugs (~109)

3.0 M6 Hot Bug Requests (~1)

3.0 M6 Hot Bugs (~0)

3.0 M6 Blockers/Criticals (~2)

3.0 M6 JST, WST, JSF Bugs Fixed (~178)

3.0 M6 JPT Dali Bugs Fixed (~49)

3.0 Untargeted Blockers/Criticals (~6)

3.0 Resolved, Unverified Blockers/Criticals (~30) By Assignee

Minutes:

Anything not in the I build today. Then pls review after I build and with PmC board

bug fixes are fine

Raghu - new features that will go into M7 from the JSF team

Angel - API change and will be talking to Tim

Kathy - might have a few features to go into M6

David - 2 types of changes, service # is fine for next week, minor field update would need to inform teams in advance

Carl - J2EE API changes that will be ready by today

Hotbug: Konstantin: Have seen more feedback from adopters, need more time for investigation

Targeted critical/blockers

Neil: Currently working on it, still have issues with reproducing. Will have a resolution by M6.

Raghu: Code fix will be checked in today

Untargeted critical/blockers

Tim: have a fix for the p2 bug, opening another bug to the p2 team

Carl:currently looking at the p2 bug

Performance Focus (Kaloyan)

Some (possible) progress on debugging the problem with running the tests. Seems related to org.eclipse.test.performance

We'll begin having weekly performance section to review tests and test results.

Update 2008-03-06: We have identified that changes made in bug 201469 could be a potential reason for the Derby error:

ERROR 42Y07: Schema 'GUEST' does not exist

The changes in the bug are about improving performance, but they also affect the org.eclipse.test.internal.performance.db.DB class and if we compare between revisions 1.68 and 1.70 we could see that the changes deal with some user and password settings. Now it is not clear what should be changed in the WTP perf tests setup to comply with this change. May be setting some user and password for Derby?!

Update 2008-03-13: We have found an interesting article about Derby that seems to explain the problem. There it is explained that if the database is accessed without authentication, then the default database schema is APP. This is our case before the changes of bug 201469. But, if authentication is used, then the default schema becomes the username. After the changes of bug 201469 all access to the DB is done through the default user Guest. The DB driver tries to find the tables in schema GUEST instead of in schema APP. This explains the Error message above.

We see the best solution is to rename the schema in our Derby database from APP to GUEST for builds after bug 201469. We are now investigating how to do this.

Minutes:

David: Generate db with platform test plugin, then things are okay, asked for the earlier build to be restored in the update site. Making progress on this, hopefully will have more report in 2 weeks

Update 2008-03-27: DB issue resolved. Just setting DB user and DB password to "app" on newer builds solves the problem. We have now perf results for M3 and M4.

It seems that we have new problems with M5. It takes much longer (~33 hours compared to ~11 hours) and the wtpperflog is huge (120 MB) and full with dumps and errors. I need some time for further investigation of the problem.

API Tools/Scans (Kaloyan)

Current ones will be ending soon. Kaloyan volunteered to explore the new Platform API tools, to make recommendations to WTP or build process.

Update 2008-03-06: I have started exploring and evaluating the Api Tooling project. It is planned to become part of Eclipse 3.4 by the end of M6. Now it is available only by checking it out from CVS.

Project overview: http://wiki.eclipse.org/PDE_UI_Incubator_ApiTools

The Api Tooling supports profiles. I need to check if this can correspond to our adopter usage reports.

There are also Batch mode tools: Binary Compatibility Reporting and API Usage Reporting, but I am still in progress to find out how to run them.

Update 2008-03-13: No progress this week. I will try to catch API Tooling developers at EclipeCon next week. They also have a Long Talk on the event.

Update 2008-03-27: I had the chance to meet Olivier Thomann. He explained me a lot about the API Tooling and gave useful advices. It seems that we would not be able to use API Tooling in the way we use our adopter API scannages. The concept of API Tooling is different. Instead we can compare for binary and source breakages between WTP releases, e.g. between 2.0.1 and 2.0.2.

Adopting API tooling requires some efforts. It is almost sure that enabling a plugin with API tooling nature will introduce lots of warnings and errors. Rules and filters must be established within the code to prevent this warnings to appear.

Other business?

David: we need to change how we generate our javadoc in the build -- project by project, or component by component.

Tim has volunteered to do something for the server project, and recommend to others (might check with Nick Bolt on this).

Teams Status and Focus for Coming Week

Source Editing

Ongoing triaging of incoming bug reports
Working on updating bug backlogs
Triaging remaining 3.0 requirements and targeted bugs

Server Tools

Web Services/WSDL

Ongoing triage of incoming and existing bugs/RFEs.
Fixing bugs and implementing RFEs.
Planning for M6.

Java EE

Dali JPT

JPT 2.0
- Released new Editor for persistence.xml
- Completed Java to JPA project conversion support
- Working on:
  - Project Explorer contribution
  - XML defaults and validation
  - EclipseLink support

JSF

Planning for M3
Property Editor prototype
JSPX support investigation
XHTML support investigation

releng

We will be changing the way we generate source features/plugins

See bug 132094 for details, implications, and links to more info.

References

Eclipse 3.4 Project Plan for the Ganymede Simultaneous Release. WTP Performance Tests Tweaking the Access Rules for WTP

Branching Strategy

Please review and comment on the WTP How to: Branching Policy and Practices guide.

In general, the minimum is if you branch a plug-in to branch all the plug-ins in the corresponding map file. It is fine to branch everything if you choose as well. We may need to reorganize map files slightly and we can investigate that on a case by case basis. This is intended to be a living document and open to evolutions and improvements.

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

WTP Smoke Test Results R30