Skip to main content
Jump to: navigation, search

WTP 2008-12-04

WTP Development Status Meeting


Project Leads
Konstantin Y
Kathy Y
Raghu Y
Helen Y
Carl Y
Amy Y
Kate Y
Angel Y
Gary Y
Eric Y

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

Announcements And Special Reports

WTP Calendar

WTP 3.0.4

WTP 304 first M build to be declared on Jan 9th 2009
Build stream currently open for code release for 304

3.0.4 Schedule

Jan 9 - M build
Jan 23 - M build
Jan 30 - RC1
All changes after Jan 30 require PMC approval (1 vote) (Official Ganymede RC1 date is Feb 4, we are declaring early)
Feb 6 - RC2 All changes after Feb 6 require PMC approval (2 votes) (Official Ganymede RC2 date is Feb 11, we are declaring early)
Feb 13 - final build
Feb 18 - 3.0.4 GA

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.
New format First draft 9/20, Final copy 10/30


  • org.eclipse.wst.xml.ui will be moving to 1.1.0 when M4 begins, prepare accordingly

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 -> Sept 26 (extra week added so not to overlap maintenance release) (updated)
M3 -> Nov 7 (short milestone, since "making up" for added week above)
3.0.3 Early Maintenance Release Nov 14
M4 -> Dec 19
M5 -> Feb 6
3.0.4 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

  • Build
Latest build has a Junit failure, smoketest on hold
  • Junit
  • Smoketest

Bug List for 3.1

Invalid 3.1 & 2.1 enhancements (~0)
Invalid 3.1 & 2.1 targeted bugs (~0)
3.1M4 & 2.1M4 enhancements (~14)
3.1M4 & 2.1M4 targeted bugs (~41)
3.1 & 2.1 enhancements (~118)
3.1 & 2.1 targeted bugs (~346)
In tabular form:
Current 3.1 & 2.1 targeted bugs (~346)
3.1 & 2.1 hotbugs (~0)
Blockers & Criticals (~3)
  • Minutes:
Reminder M4 is declaring on December 19th
critical bug
Konstantin - there should be 2 PMC signoffs for API change, this would be a serious issue once 304/eclipse 342 is available for all adopters to adopt next year
Chuck - breaking in the case when you're creating a brand new project which is not one we're providing in WTP
bad problem we will look into fixing, but not necessariy reverting the original changes
will watch for updates on this issue

Other business

  • Minutes:

Previous items for reference

WTP Build status page
Status page link
WTP UI Walkthroughs
Three New Incubator proposals
Visual Editor for XML (VEX)
bug 169810
XML Security Tools Proposal
bug 243106
XQuery Proposal
bug 225394

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
  • Planning M4 and 3.0.4

Server Tools

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

Back to the top