Skip to main content
Jump to: navigation, search


WTP Development Status Meeting 2007-08-16


John L, David W, Nitin D, Larry D, Neil H, Jess G, Rob F, Kathy C, Tim D, Amy W, Carl A, Konstantin K, Kate P


Action Items

The goal is to finish these by end of M1.
  • Progress on Bug Backlog To Do's (Maybe we should add a date to the query to only show true backlog bugs?)

WTP 3.0

Still waiting on plans from Eclipse for the Ganymede release schedule, but anticipate us to follow their 6 week milestones by 2 weeks for the first 3 milestones.

WTP M1: 8/24

Ganymede Simultaneous Release

Requirements Review

Update from conference call with the community on the WTP 3.0 Requirements? See the minutes.
Not much community participation in the meeting so this may not be the best format next time.
  • Planning
  • Project/Component Leads: We have one action item. Please update the bugzilla for enhancement requests planned for 3.0 to include the keyword, plan. This will help in getting an accurate list of the work from the query on the Requirements Main page.
  • The next step will be WTP 3.0 planning, and we expect this to be ongoing through end of August and middle of September with feedback from community taken into consideration.

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.
Performance Test Owners
  • wst-common - Konstantin
  • wst-css - Nitin
  • wst-html - Nitin
  • wst-server - Angel
  • wst-wsdl - Valentin
  • wst-xml - Nitin
  • wst-xsd - Valentin
  • jst-j2ee - Carl
  • jst-jsp - Nitin
  • jst-server-tomcat - Angel
  • jst-ws - Kelvin Cheung
  • jst-jsf - Raghu - to be added in 3.0
  • jpt - Neil - to be added in 3.0

Latest Results
WTP 2.0
Known Issues
  • Performance Test Bugs and Enhancements
  • Improve the actual tests. Why do some take so long? Why do some results fluctuate? Why do some have drastic performance degradations? Are the tests even still valid?


  • M1 Schedule?
July 2007 - August 2007
Monday Tuesday Wednesday Thursday Friday
Status Call
Status Call
Thumbs Up Test
Declare WTP 3.0 M1

How are we looking in terms of delivering an M1?
Changes in Internal API we use from the platform? Done.
Tomcat to Jetty changes? Still in progress, more work than originally thought including some restructuring.
Plug-in dependency range updates? Done.
Tabbed properties view changes?
Clean build? Done.
JUnits passing? 4 failures in JSF and JPT.
New and Noteworthy? preview.

  • Bug Lists
3.0 M1 Targeted Bugzilla Enhancements (~4)
All Remaining 3.0 Targeted Enhancements (~130)
3.0 M1 Remaining Targeted Bugs (~13)
3.0 M1 Hot Bug Requests (~2)
3.0 M1 Hot Bugs (~0)
3.0 M1 Blockers/Criticals (~0)
3.0 M1 JST, WST, JSF Bugs Fixed (~16)
3.0 M1 JPT Dali Bugs Fixed (~0)
3.0 Untargeted Blockers/Criticals (~0)
3.0 Resolved, Unverified Blockers/Criticals (~5) By Assignee

WTP 1.5.5

WTP Release 1.5.5 Schedule

Remember 2 votes are required for PMC approval for 1.5.5.
Aug 10 RC1
Aug 17 RC2 (only if needed for blocking bugs or major regressions)
Aug 24
Aug 31 1.5.5 GA
  • If you fix a 1.5.5 bug, please open a separate 2.0.1 bug.
  • Build Status
JUnits are still all blocked by J2EE deadlock bug
We are waiting on 199520 and then on Friday we will smoke test the latest 1.5.5 build this week to declare RC2.
  • Test Plans and Results
WTP Release 1.5.5 Functional Regression Test

  • Bug lists (WST,JST,JSF)
Invalid Targeted Defects <1.5.5 (~1)
1.5.x Untargeted Blockers/Criticals (~0)
1.5.x Untriaged Bugs (~0)
1.5.5 Bugs for WTP PMC review and approval (~2)
1.5.5 Hot Bug Requests (~0)
1.5.5 Hot Bugs (~2)
1.5.5 Blockers, Criticals (~3)
1.5.5 Remaining Targeted Bugs (~7)
1.5.5 Total Bugs Fixed (~79)
All Bugs Fixed in 1.5.x Releases
1.5.x Resolved, Unverified (~57)
1.5.x Verified, Not closed (~0)

WTP 2.0.1

Aug 17 M Build
Aug 31 M Build
Sept 07 RC1 (PMC approval 1 votes)
Sept 14 RC2 (PMC approval 2 votes)
Sept 21 (if necessary, PMC approval 3 votes)
Sept 28 2.0.1 GA

  • 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.
  • Build Status
JUnits are all passing
Please smoke test the latest 2.0.1 build to declare this week's 2.0.1 M Build by end of day.
  • Bug Lists
All Remaining 2.0.1 Targeted Bugs (~153)
2.0.1 Hot Bug Requests (~2)
2.0.1 Hot Bugs (~0)
2.0.1 Bugs for PMC Approval (~0) Starts August 31st...
2.0.1 Untargeted Blockers/Criticals (~1)
2.0.1 Blockers/Criticals (~6)
2.0.1 Total JST, WST, JSF Bugs Fixed (~65)
2.0.1 Dali Total Bugs Fixed (~18)
2.0.1 Resolved, Unverified Blockers/Criticals (~7) By Assignee

Bug Backlogs

All Untriaged WTP Bugs (Graph)
All Untriaged WTP Bugs (~120)
All WTP Verified, Not Closed Bugs (Graph)
All WTP Verified, Not Closed Bugs (~0)
All WTP Resolved, Unverified Bugs (Graph)
All WTP Resolved, Unverified Bugs (~783)
All WTP Defect Backlog (Graph)
All WTP Defect Backlog (~3379)
All WTP Future Bugs (~37)
All Open WTP Bugs with Patches Attached (Graph)
All Open WTP Bugs with Patches Attached (~237)
All API Requests (~9)

Working Groups

  • Java EE 5
Web Tools Platform Release 3.0 JavaEE Requirements
JEE5 Test Scenarios

  • Website
Bob F?

Other business?

Teams Status and Focus for Coming Week

Server Component Team

Datatools (RDB, 1.5.x only)

XML/JSP Component Team

  • Verifying 1.5.5 fixes while regression testing
  • Working on fixes for 2.0.1
  • Finally looking at our bug backlogs now that 1.5.5 is forcibly shutting down.
  • Ongoing triaging of incoming bug reports

Web Services Component Team

  • Working on fixes for 2.0.1
  • Working on porting the Web Services Explorer to Jetty for WTP 3.0 M1 -- 192785
  • Ongoing triaging of incoming bug reports.
  • Verifying defects.

Java EE Component Team

Dali JPT



API Violations Review

Visit latest build for current API violations.
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?


  • 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 3.0 Smoke Results Page
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

Back to WTP Meeting Archives
Back to Web Tools Wiki Home

Back to the top