Skip to main content
Jump to: navigation, search

WTP 2008-02-28

WTP Development Status Meeting 2008-02-28


Project Leads
Tim Y
Nitin Y
Kathy Y
Chuck Y
Raghu Y
Neil Y
David Y
Helen Y
Philippe Y
Bob Y
Carl Y
Kaloyan Y
Larry Y
Angel Y
Brad Y
Nick Y

Announcements And Reports

  • WTP 2.0.2 delivered Monday Feb 25, Congrats & Thank you! : )
  • Europa Simultaneous Release on Friday, 2/29!

Focus on Backlog and Quality metrics (Neil)

Current Focus Item
  • Options are
  • Target bug for a release or "future"
  • Mark as Invalid or Wont Fix
Minutes: Note sent to Kate Price (Documentation) (current leader at 6 ... though seveal 5s too)

Upcoming Focus Item
Past Focus Items
  • 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.
  • Before July 1st, 2007 - 21
Where did they all go?

Focus on Requirements Planning (Raghu)

Projects with no committed items: none
Please update status page
  • Please review untriaged enhancement requests
Untriaged Enhancement Requests ()
  • 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

WTP 2.0.2

Done, Thank you!
  • Download
  • 2.0.2 Release Page
  • Test Results
  • Last M Build Jan 18
  • Feb 1 RC1
  • Feb 15 RC2 (RC2, bugs from Feb 1 - Feb 15 will need 1 PMC approval vote)
  • Feb 22 RC3 (RC3 only if necessary, bugs from Feb 15 -> Feb 22 will need 2 PMC approval votes)
  • Feb 25 2.0.2 WTP GM
  • Feb 29 2.0.2 Public access
  • Bug Lists
All Remaining 2.0.2 Targeted Bugs (~5)
2.0.2 Hot Bug Requests (~0)
2.0.2 Hot Bugs (~0)
2.0.2 Bugs for PMC Approval (~0)
2.0.2 Untargeted Blockers/Criticals (~1)
2.0.2 Blockers/Criticals (~0)
2.0.2 Total JST, WST, JSF Bugs Fixed (~97)
2.0.2 Dali Total Bugs Fixed (~8)
2.0.2 Resolved, Unverified Blockers/Criticals (~22) By Assignee
  • Minutes:
Remaining 2.0.2 Targeted Bugs to be closed if already fixed or moved out of 202

Post WTP 2.0.2

  • Currently 3 known "bad bugs" (critical, major, hotbugs)
  • Do we need a 2.0.3 release?
  • The PMC recommends we produce official patches, regression test, and release those to update site

Minutes: No objections. David to update process docs and propose specific dates.

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

  • Builds
Propose we can smoke test on I20080228113529 or later (another done in about an hour, but even it will have JUnit failures?)
And need to fix versioning errors.
Build Breakages Board
Current build has 3 compile and 4 Junit failures
Smoketest not yet issues
3.0 Smoketest results
  • Bug Lists
3.0 Invalid Targeted Bugs (~3)
3.0 M6 Targeted Bugzilla Enhancements (~24)
All Remaining 3.0 Targeted Enhancements (~164)
3.0 M6 Remaining Targeted Bugs (~138)
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 (~51)
3.0 M6 JPT Dali Bugs Fixed (~28)
3.0 Untargeted Blockers/Criticals (~0)
3.0 Resolved, Unverified Blockers/Criticals (~32) By Assignee
  • Minutes:

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.

API Tools/Scans

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

Other business?

Any questions? Objections?
No objections ... committers reminded to stay familiar with it, as it documents "permissible changes" and other processes.
  • Do we still need component.xml files? (from the platform)
None known.
  • Are there volunteers to explore (and make recommendations on) the Platforms new API tools?
Kaloyan will look into them.
  • 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).
  • We will be changing the way we generate source features/plugins
See bug 132094 for details, implications, and links to more info.
  • Design meetings ... are they happening?
JSF-SSE-Validation? (Nitin will follow up).
JSDT-Facets? (Brad thought would still be worth while, perhaps walk through of current design/behavior).
  • Introductions: Philippe introduced himself (as new lead of ATF Project). Gave brief description of current dependencies (core, server, sse) and plans related to WTP (esp. WYSIWYG editor).
  • Brief discussion of broken link on WTP page ... turned out to be a bad URL in our project metadata.
And mentioned Helen will be tracking down other broken links :)

Teams Status and Focus for Coming Week

Source Editing

  • Ongoing triaging of incoming bug reports
  • Working on updating bug backlogs
  • Planning for M6

Server Tools

Web Services/WSDL

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

Java EE

Dali JPT


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


  • will soon remove wst common ui properties. See bug 131862.
  • will soon start signing all jars. Teams will have to be on the look out for performance problems, in M6. If any, it would effect those cases where custom class loaders are used, as that might result in repeated class



  • Branching Strategy
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
Information about process for milestone bugzilla line item planning has been added to the WTP Bugs, Workflow, and Conventions document.
PMC Candidate Review Request Checklist - See the updated PMC Review document with attention to the "How To Prepare a PMC Defect Candidate" section
Adopter Migration Information for WTP 2.0 - Please add any details for your component.
  • Website
Documentation on Setting up your system for Web Tools Web site development and Using Web Tools Phoenix PHP templates is on the wiki at Web Tools Web Site Development.
  • Bug Day
Monitor and participate in Bug Day if you would like.
Mark any applicable bugs with keyword "bugday", but only if you'll have a representative on hand to respond through Bugzilla or in IRC
Current WTP Bug Day bugs (~53)

Bug Backlogs

All Untriaged WTP Bugs (Graph)
All Untriaged WTP Bugs (~227)
All WTP Verified, Not Closed Bugs (Graph)
All WTP Verified, Not Closed Bugs (~159)
All WTP Resolved, Unverified Bugs (Graph)
All WTP Resolved, Unverified Bugs (~1532)
All WTP Defect Backlog (Graph)
All WTP Defect Backlog (~3168)
All WTP Future Bugs (~166)
All Open WTP Bugs with Patches Attached (Graph)
All Open WTP Bugs with Patches Attached (~229)
All API Requests (~9)

Back to WTP Meeting Archives

Back to the top