Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: for the plan.

Jump to: navigation, search

WTP 2008-09-11

WTP Development Status Meeting


Project Leads
Konstantin Y
Tim Y
Kathy Y
Kaloyan Y
Raghu Y
Neil Y
David Y
Helen Y
Carl Y
Dave Y
Phil Y
Larry Y
Amy Y
Kate Y
Angel Y
Nick Y

Note: feel free to correct any errors/omissions in above attendance record.

Announcements And Special Reports

Updated Participant Passcode for dev mtg: 269746

This passcode will be changing every few months, the main dev status page will be updated with the info, pls watch out for it. Thanks!

WTP 3.0.2

Aug 29 - M build
Sept 5 - RC1 (All changes after RC1 require ONE PMC approval votes)
Sept 12 - RC2 (All changes after RC2 require TWO PMC approval votes)
Sept 19 - RC3 & final build
Sept 25 - GA
  • Build & Smoketest
Smoketest will be issued once new build is available

Bug Lists for 3.0.2

PMC Approval Summary List
Blockers & Criticals (~8)
All 3.0.2 Hotbugs (~3)
Current 3.0.2 & 2.0.2 targeted bugs (~102)
In tabular form:
Current 3.0.2 & 2.0.2 targeted bugs (~102)

Fixed Bugs

Web Tools
Number Fixed for 3.0.2 (~70)
Java Server Faces
Number Fixed for 3.0.2 (~8)
Dali JPA Tools
Number Fixed for 2.0.2 (~9)
  • Minutes:
Patch for a Dali bug, not urgent for this week
Tim: need to be released to the 301 patch stream, not urgent for RC2 this week, but needed in 302
Neil: will release
232251: Kaloyan: can wait till next week
244392: Angel will look after mtg
245573: Neil: will target for the next minor 2.1 release, not for 30x release
245851: Amy: might not be for 302
245965: Jason is looking at it
246294: will send Nitin a note
246624: not for this week, need it for the 302 stream, will submit for PMC approval
246702: Nick, will take a look at this one
243883: Tim: will submit for next week PMC
Kaloyan: good for 302, don't need it for this week
245263: Amy: fix is attached, need feedback from submitter
Kaloyan: will ask collegue to answer

WTP 3.1


WTP 3.1 Project Plan

Two issues came up when discussing the planning process

  1. How to handle "future" milestone target? Turns out we have discussed and documented this before, see WTP_Bugs, Workflow and Conventions#The meaning of "Future" milestone target.
  2. How can we better incorporate bugs-to-fix in 3.1 planning? Subsequent to meeting, I suggested that leads/committers should set the 3.1 milestone target for bugs that ideally should be fixed in 3.1, to help "prime the pot". For example, nearly all voted on bugs and "major" bugs should be so marked. I've added more bugzilla queries to WTP 3.1 Project Plan to assist.


Adjusted schedule, based on Platform's proposed schedule.

Normally, our milestone are one week after the Platform's delivery. Exceptions noted below.

3.0.1 Early Maintenance Release Aug 15
M1 -> Aug 22 (extra week added so not to overlap maintenance release)
3.0.2 Coordinated Maintenance Release Sep 24
M2 -> Oct 3 (extra week added so not to overlap maintenance release)
M3 -> Nov 7 (short milestone, since "making up" for added week above)
M4 -> Dec 19
M5 -> Feb 6
3.0.3 Coordinated Maintenance Release Feb 25
(EclipseCon March 23-27)
M6 -> Mar 20 Feature Complete, API Freeze, UI Freeze, NLS, Accessibility
M7 -> May 8 Performance tuning, documentation, bug fixing
RC1 -> May 22 Serious bugs only, focus on stability.
RC2 -> May 29 WTP will likely not participate in an RC2, based on feedback from last year that RC2 came too soon, needed more fixing, less testing
RC3 -> Jun 5 Very serious bugs only.
RC4 -> Jun 12 Very very serious bugs only.
RC5 -> Jun 19 Hopefully no changes from RC4. Prepare web pages, update sites, etc.
GA -> Jun 24

Build & Smoketest

  • waiting for build to complete before sending out smoketest

Bug List for 3.1

Invalid 3.1M1 & 2.1M1 enhancements (~0)
Invalid 3.1M1 & 2.1M1 targeted bugs (~0)
3.1M2 & 2.1M2 enhancements (~5)
3.1M2 & 2.1M2 targeted bugs (~10)
3.1 & 2.1 enhancements (~98)
3.1 & 2.1 targeted bugs (~223)
In tabular form:
Current 3.1 & 2.1 targeted bugs (~223)
Blockers & Criticals (~9)
3.1 & 2.1 hotbugs (~0)
  • Minutes:
David: no build available yet, cannot find org.eclipse.jpt
Neil: made some change to remove things from the build and that had caused some problems, will look into it and resolve

Other business

WTP UI Walkthroughs
Thre New Incubator proposals
Visual Editor for XML (VEX)
bug 169810
XML Security Tools Proposal
bug 243106
XQuery Proposal
bug 225394
  • Minutes:
Dave C: new project -> visual editor for XML, 1 committer coming over from platform, will add link here
David: great addition

Teams Status and Focus for Coming Week

Performance Team

The minutes of the meetings are posted. Next meeting is next Monday same time. See details on the wiki page: WTP Performance Tests

Source Editing

  • Ongoing triaging of incoming bug reports
  • Working on 3.0.2
  • Deciding overall themes and plan for 3.1

Server Tools

- Last week we update the landing website, to include revised defect queries and new format (

- Completed plan for 3.1

Web Services/WSDL

  1. Ongoing triage of incoming and existing bugs.
  2. Fixing and verifying bugs.

Java EE

JEE Status Meetings

Dali JPT

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


  • Feature exceptions
  • Bug Fixes


  • triage/planning


In general, the minimum requirement is that if you branch a plug-in, you need to branch all the plug-ins in the corresponding map file. This is to make it easier for others to know what to load, to "be current" in a maintenance branch. It is fine to branch everything in a sub-project if you choose to, but still need to correspond to what's in a map file, and the map file should be updated to explain what it's used for. Map files can be re-organized some, if that helps make it easier to organize and understand what teams are working on what.
The names for branches should follow the pattern of 'R3_0_maintenance'. This will be the name for all 3.0.x maintenance work (not just the first, 3.0.1 maintenance work). Note that JSF and JPA code may use R2_0_maintenance, but their map files, will still be branched using R3_0_maintenance.
  • 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)

Project Meta data, for Project leads, especially, see "information about ..." from your subproject web page left nav bar.
Go to Foundation Portal
Login with committer ID
Click on "[maintain] Project Info meta-data"
Changes coming to IP Log management (more automated, but more for Project Leads to do?): See Development Resources/Automatic IP Log

Copyright © Eclipse Foundation, Inc. All Rights Reserved.