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-08-14

WTP Development Status Meeting


Project Leads
Konstantin Y
Nitin Y
Chuck Y
Raghu Y
Neil Y
Helen Y
Carl Y
Phil Y
Larry Y
Kate Y
Angel Y
Brad Y
Valentin Y

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

Announcements And Special Reports

WTP 3.0.1

Aug 1 - RC2
All changes after Aug 1 require PMC approval (2 votes)
Aug 8 - RC3
Aug 15 - RC4 & final build
Aug 22 - 3.0.1 GA

Bug Lists for 3.0.1

PMC Approval Summary List
Blockers & Criticals (~6)
All 3.0.1 Hotbugs (~3)
Current 3.0.1 & 2.0.1 targeted bugs (~0)
In tabular form:
Current 3.0.1 & 2.0.1 targeted bugs (~0)

Fixed Bugs

WOW! Congratulations!
Web Tools
Number Fixed for 3.0.1 (~257)
Java Server Faces
Number Fixed for 3.0.1 (~4)
Dali JPA Tools
Number Fixed for 2.0.1 (~30)
  • Minutes:
    Helen will issue smoketest request for build one 243834 is available in build
Next week is test week, test plan created above, pls update
  • PMC request
243183: Brad - too late for PMC 301, will retargetd for 302
243623: Neil - too late for hotbug to approve for 301
Raghu - approving per hotbug request, but would rather have it for 302
Peter - taking a while in the adopter product

243747: Raghu - medium risk, too much change
Neil - candidate for 302, maybe patch on top of 301
Chuck - possibile patch for 301
Carl - possibly a 201 patches for Dali
Nitin - will work with that
243834: Chuck - regression
Neil - approve
Raghu - approve
243869: Konstantin/Neil - negative impact on adopters? version transitions are not allowed
Chuck - discussed on wtp-dev for WTP 31
Neil - will need to read through the comments
Raghu - for 302, wtp-dev so other adopters can take a look into them
  • Criticals/Blockers:
243547: Neil - waiting for the reporter to reproduce
Chuck - there are ppl running these scenarios while Gary is out, will fup and update
194047 - Phil: will target for 302
233165 - 3.1
243450 - 3.1M1
243547 - 301 blocker, has propsed patch, need more update
243559 - 202
243662 - 301 PMC request
243727 - 301 blocker(found by smoketest), awaiting PMC approval
243869 - 301 blocker
243934 - regression for 301, awaiting PMC approval

WTP 3.1


WTP 3.1 Project Plan

Bi-weekly smoketest before we declare M1

Delaying smoketest to August 21st, 1 smoketes before M1, any objections?
August 7th
August 21st
M1 declared on August 22nd (please complete the New and Noteworthy beforehand)

Two issues came up when discussing the planning process

  • Minutes:
Raghu - more time to do the final plan, dates are updated in plan link
No objections to one M1 smokestest next Thursday and declare on Friday

  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

Other business

Project leads: please fix meta-data during July. 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
In the works: Proposal to adjust bugzilla so bugzilla "products" match our subcomponents (currently have 4, need about 8?)
WTP UI Walkthroughs

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 final 3.0.1 submissions
  • Deciding overall themes for 3.1

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)

Back to the top