Skip to main content
Jump to: navigation, search

WTP 2008-02-14

WTP Development Status Meeting 2008-02-14


Project Leads
Konstantin Y
Tim N
Nitin Y
Kathy Y
Chuck N
Naci N
Raghu Y
Neil Y
David Y
Helen Y
Bob N
Carl Y
Dave N
Phil Y
Kaloyan Y
Larry N
Amy Y
Kate Y
Angel Y
Rob Y
Brad Y
Nick Y

Announcements And Reports

  • WTP 2.0.2 Shutdown, RC2 this week, 2 PMC approval vote needed for RC2 inclusion
  • WTP 3.0 M5 to be declared on Monday 2/18

Focus on Backlog and Quality metrics (Neil)

Neil: Current focus item updated
  • Current Focus Item:
  • Options are
  • Target bug for a release or "future"
  • Mark as Invalid or Wont Fix
  • 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?

WTP 2.0.2

  • 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
  • Build
RC2 build M-2.0.2RC2-20080214103812/
2.0.2 RC2 Smoketest

  • 202 Shutdown Test Plan
202 Shutdown

  • Bug Lists
All Remaining 2.0.2 Targeted Bugs (~19)
2.0.2 Hot Bug Requests (~0)
2.0.2 Hot Bugs (~0)
2.0.2 Bugs for PMC Approval (~1)
2.0.2 Untargeted Blockers/Criticals (~0)
2.0.2 Blockers/Criticals (~0)
2.0.2 Total JST, WST, JSF Bugs Fixed (~91)
2.0.2 Dali Total Bugs Fixed (~10)
2.0.2 Resolved, Unverified Blockers/Criticals (~21) By Assignee
  • Minutes:
Helen: 202 shutdown test plan created. Please update before we're done on 2/25.
For RC2, need for RC3 respin?
Amy: 1 change for version update
Neil:JPA may need to update for service numbers as well
David: these changes are allowed next week as well,
Kathy: verion checking enabled?
David: RC2 will have the acurate reference data for RC1. That build will be complete this evening.

WTP 3.0 M5

  • our +2 date: Monday, February 18 2008
  • Final Code released by Feb 8th
Plan 01/07 - 01/11
Development 01/14 - 02/08
Test 02/11 - 02/15
  • Builds
2 compile errors in performance test, fix released

  • Bug Lists
3.0 Invalid Targeted Bugs (~1)
3.0 M5 Targeted Bugzilla Enhancements (~9)
All Remaining 3.0 Targeted Enhancements (~166)
3.0 M5 Remaining Targeted Bugs (~36)
3.0 M5 Hot Bug Requests (~0)
3.0 M5 Hot Bugs (~0)
3.0 M5 Blockers/Criticals (~1)
3.0 M5 JST, WST, JSF Bugs Fixed (~142)
3.0 M5 JPT Dali Bugs Fixed (~1)
3.0 Untargeted Blockers/Criticals (~0)
3.0 Resolved, Unverified Blockers/Criticals (~31) By Assignee

3.0 M5

Helen: Please complete M5 testplans before Monday
Move both targeted enhancement for M5 and targeted M5 bugs off M5
Angel: 218982 critical bug will be released shortly
David: builds will still be automatically triggered after code release
M5 -> mark them as fixed or move them to the next milestone, targeted enhancement and bugs

Other business?

Teams Status and Focus for Coming Week

Server Tools

Source Editors

  • Ongoing triaging of incoming bug reports
  • Shutting down for 3.0 M5 and 2.0.2 RC2

Web Services/WSDL

  1. Ongoing triage of incoming and existing bugs/RFEs.
  2. Planning for M5.

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