WTP 2008-03-13

WTP Development Status Meeting 2008-03-13

Attendees

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

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

Friends
Nick	Y

Announcements And Reports

EclipseCon WTP Committers BOF, Monday evening.

Minutes:

Will be cancelling mtg next week due to eclipseCon, will communicate through email for smoketest and I build will be declared

Canadian holiday, good Friday next week as well

David: BOF scheduled on Monday 17th to talk about general process, meet and greet

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

Patches are ready to test. We'd like all teams to give brief smoke test with all patches applied, just to confirm no obvious side effects. Those teams that contributed the fixes should test to confirm their fixes are in the build correctly.

Plan is to put on official /webtools/updates on Friday, as soon as smoke tests complete.

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

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

220297

219889

219627

Patch creation instructions
Patch download site
Smoketest

The PMC recommends we produce official patches, regression test, and release those to update site

Minutes:

Patch build ready, Helen will send out smoketest request, please smoketest by noon tomorrow to be available before eclipseCon, teams provided the fix please pay more attention to verify the fixes

Carl: another blocker opened towards 202, 222531

Rob: potentially working as designed

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

Builds

Build Breakages Board

35 Junit failures on latest build - I20080313113126

30 in JEM -> 28 are due to build machine issues, as they arepassing on local build machine, investigating the other 2

2 in JEE -> under investigation

1 in DTD -> will not affect smoketesting

3.0 Smoketest results

Bug Lists

3.0 Invalid Targeted Bugs (~3)

3.0 M6 Targeted Bugzilla Enhancements (~31)

All Remaining 3.0 Targeted Enhancements (~156)

3.0 M6 Remaining Targeted Bugs (~154)

3.0 M6 Hot Bug Requests (~0)

3.0 M6 Hot Bugs (~0)

3.0 M6 Blockers/Criticals (~1)

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

3.0 M6 JPT Dali Bugs Fixed (~36)

3.0 Untargeted Blockers/Criticals (~2)

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

Minutes:

David: Nitin contributed Junit changes to the current build

restarted cruisecontrol that was potentially causing the 28 of the JEM failures

Carl: Junit changes commented out for the build after the currently running one

David: Issue with moving up prereqs for JPT

Neil: platform changes that affects the JPT code, suspecting its an API change that's affecting JPT, hopefully just for this week, will figure out an alternative approach for next week's I build

Blockers/Criticals bugs

Neil: 220670: haven't heard back from the adopters in the new code, nothing that will be resolved right away, will look into it for M6

David: JSF bug 206514: looks like fix is already available, just didn't make it into this week's I build

Untargeted blockers/critical bugs

Larry: this is not a critical issue, will adjust severity

214888: Helen will send a note to Gerry on this one for update

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

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.

Other business?

Meeting next week? Cancelling

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
Working on 3.0 requirement for more configurable XML and HTML formatting (95091,194698)

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