Skip to main content
Jump to: navigation, search

WTP 2008-10-23

WTP Development Status Meeting


Project Leads
Konstantin Y
Tim Y
Nitin Y
Kathy Y
Chuck Y
Kaloyan Y
Raghu Y
Neil Y
David Y
Helen Y
Bob Y
Carl Y
Dave Y
Phil R
Larry Y
Amy Y
Kate Y
Angel Y
Valentin Y
Gary Y

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

Announcements And Special Reports

  • Please document cases that require increasing the lower prereq bounds to Galileo stream.

See A study of prereq lower bounds

  • EclipseWorld - 28 - 30
  • Minutes:
David: Pls document those cases when we have to increase lower bound, raise awareness to this issue and eventually maybe some process
EclipseWorld next week, we'll still have dev mtg and record mtg for those who are not around. Have fun!

WTP 3.0.3

10/03 M build
10/17 M build
10/24 RC1 (PMC review starts after RC1, initially one vote)
10/31 RC2 (after RC2, two PMC votes)
11/7 RC3 (after RC3, three PMC votes)
11/14 3.0.3 Release

Build & Smoketest

  • Build
M-3.0.3-20081023125735 sent for smoketest
  • Junit
  • Smoketest
Smoketest Results

Bug Lists for 3.0.3

Blockers & Criticals (~1)
All 3.0.3 Hotbugs (~1)
Current 3.0.3 & 2.0.3 targeted bugs (~112)
In tabular form:
Current 3.0.3 & 2.0.3 targeted bugs (~112)

Fixed Bugs

Web Tools
Number Fixed for 3.0.3 (~133)
Java Server Faces
Number Fixed for 3.0.3 (~0)
Dali JPA Tools
Number Fixed for 2.0.3 (~3)
  • Minutes:


Carl: currently investigating, working with JBOss


251908: Carl: deadlock issue, just opened, looking into it
Kaloyan: not critical for this week, but need it for the 303

Currently targeted bugs

Please triage, 112 currently for 303 while we're entering RC mode

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


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
I-3.1-20081023110843 sent for smoketest
Minor version updates done, all teams affected has reacted to these changes?
  • Junit
2 junit failures in JEE, 251660 to be released to address this
  • Smoketest
Smoketest Results, pls update by 3PM tomorrow

Bug List for 3.1

Invalid 3.1 & 2.1 enhancements (~0)
Invalid 3.1 & 2.1 targeted bugs (~0)
3.1M3 & 2.1M3 enhancements (~22)
3.1M3 & 2.1M3 targeted bugs (~48)
3.1 & 2.1 enhancements (~101)
3.1 & 2.1 targeted bugs (~257)
In tabular form:
Current 3.1 & 2.1 targeted bugs (~257)
Blockers & Criticals (~1)
3.1 & 2.1 hotbugs (~1)
  • Minutes:

Minor version update in build

Konstantin: Done, thanks everyohe


251756: Neil: will release for next week

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:
Visual Editor => going under initial review, and approval to check code into CVS
XML Security => going through IP review
XQuery => final paper work, done IP review

Build subscription information

Build notification list added: Angel, Nitin, Neil, Raghu
Kaloyan: WTP performance call on Mondays moved to today as a section on WTP Performance
Last meeting defined open action items, listed under WTP performance wiki page
Anyone has any comments on those to note there
Gary: Questions on instruction, running for a development environment?
Kaloyan: Yes for now dev only

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.3 and M3
  • Deciding overall themes and plan 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)

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