Skip to main content
Jump to: navigation, search

WTP 2008-05-08

WTP Development Status Meeting 2008-05-08


Project Leads
Nitin Y
Kathy Y
Neil Y
David Y
Bob Y
Carl Y
Dave Y
Kaloyan Y
Kate Y
Angel Y
Nick Y

Announcements And Reports

M7 is done ... note to go out soon, news item next Monday for "simultaneous release".

Focus on Requirements Planning (Raghu)

Done. PMC will "close out" soon.

Do we need a full-team post-mortem on requirements/planning process? Answer: No, just during full release post mortem suffices.

Start on 2009 plan: June - September.

Post WTP 2.0.2

  • Done for now, but .... some issues are still being investigated.
  • 201318 EAR Libraries container fails to initialize for 2...
  • 230256 [hotbug_request] jst.jee JEEDeployableFactory refuses to load ejb3 module
  • 222531 Regression (?) between wtp 2.0.1 and 2.0.2 in J2EEFlexPro..
  • Minutes:
201318 Carl will be working on soon.
230256 Carl needs to discuss with Chuck (and Chuck's been out).

WTP 3.0 End-Game

We are now in phase where stability is most important and fix only the worst, safest bugs.

One PMC review required before releasing to build. (All PMC should review, and any can veto, even once approved, though would be rare, and with good reason).

User/SDK docs can be updated up to RC1 without PMC approval, beyond which PMC approval will be needed

WTP 3.0 Ramp down Plan for Ganymede


RC1 05/20
Code done by Wed. 5/14
Smoke tests on Thursday 5/15
"Unofficial Declare" on Friday 5/16
Make official on Tuesday 5/20
Upcoming Holidays:
5/19 Victoria Day (Canada)
5/26 Memorial Day (US)

Upcoming Schedule

RC2 05/27
Code done by Wed. 5/21
Smoke tests on Thur. 5/22
"Unofficial Declare" on Friday 5/23
Make official on Tuesday 5/27
RC3 06/02
Code done by Wed. 5/28
Smoke tests on Thur. 5/29
"Unofficial Declare" on Friday 5/30
Make official on Monday 06/02
RC3 06/09
Code done by Wed. 6/4
Smoke tests on Thur. 6/5
"Unofficial Declare" on Friday 6/5
Make official on Monday 6/9
Ganymede 06/16
Code done by Wed. 6/11
Smoke tests on Thur. 6/12
"Unofficial Declare" on Friday 6/14
Make official on Monday 6/16


All builds should be "good"

Why do we still have so many JUnit failures?

Answer: unknown (but, are hard to reproduce).

Does the Build Breakages Board help?

Answer: yes, still does some good. Suggestion to make builds more modular so they can be quicker -- I agree need to be quicker, but not sure of best way to do that ... except we can (probably) run each build in it's own process, so XSL doesn't have to wait for WTP to finish. (But, will take some work, so will take a while).


Final Release Test Plans? Helen to coordinate/announce soon.

Bug Lists to Ramp Down

All Blockers and Criticals (~5)
All Hot Bugs and Requests (~3)
All Remaining Targeted Enhancements (~22)
Remaining Targeted Bugs (>350)
Resolved but Unverified Blockers/Criticals (~46) By Assignee
Invalid Targets (~0)

Minutes: It was mentioned we need a 3.0.1 target, to better re-target some of the bugs.

Release Review Requirements

  • Need zip file of about.html files by 5/15
  • Review will be first or second week of June

IP Log

  • In general, Project leads should review our IP Log for completeness and correctness.
  • non-Committer Contributions
* bugzillas with contributed patches should be marked with contributed keyword
* There are some WTP IP Tools to help explore potential contributions.


  • Make sure copyrights are up-to-date and according to Eclipse Foundation form:
See Default Eclipse Foundation Copyright and License Notice

Check for "license files"

  • Check 'about.html' files exists
  • are valid
  • have correct "layout" in directories
  • References:
In the general eclipse legal section
Is one page that speaks to the about files directly
In particular, note there are two that refer to literal HTML only versions, to use as your starting point.
Also, please read
It goes into detail about the locations, needs for plugins and features, and also mentions that third party content requires a seperate license file.

Performance Focus (Kaloyan)

No progress for the last two weeks. Still fighting with the Results Graph Generator.

API Tools/Scans (Kaloyan)

Can we run reports? Though they are hard to spot errors since out of date ... perhaps we can "diff" reports?

Other business

Had good discussion of what the JavaDoc issues are, with promises to follow up on wtp-releng.

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

  1. Ongoing triage of incoming and existing bugs.
  2. Fixing bugs.
  3. Planning for M7.

Java EE

Dali JPT

  • JPT 2.0
    • Working on:
      • EclipseLink support
      • Bugs for M7
      • Performance


  • Feature exceptions
  • Bug Fixes


  • We will be changing the way we generate source features/plugins
See bug 132094 for details, implications, and links to more info.


  • 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 (~244)
All WTP Verified, Not Closed Bugs (Graph)
All WTP Verified, Not Closed Bugs (~398)
All WTP Resolved, Unverified Bugs (Graph)
All WTP Resolved, Unverified Bugs (~2098)
All WTP Defect Backlog (Graph)
All WTP Defect Backlog (~3131)
All WTP Future Bugs (~422)
All Open WTP Bugs with Patches Attached (Graph)
All Open WTP Bugs with Patches Attached (~205)
All API Requests (~9)

Back to WTP Meeting Archives

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
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?
  • Minutes:
Neil: will focus on untargeted enhancements again after Release of 3.0

Back to the top