Skip to main content
Jump to: navigation, search


Revision as of 13:49, 18 May 2007 by (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

WTP Development Status Meeting 2007-05-17


John L, Nitin D, Amy W, Carl A, Raghu S, Jess G, Konstantin K, Scott L, Bob F, Dave G, Larry I, Tim D, Kathy C, David W, Neil H, Larry D, Chuck B, Angel V


  • Congratulations to Kaloyan Raev from SAP for being voted a committer!
  • ECLIPSE SUMMIT EUROPE 2007 October 9-11, 2007 in Stuttgart, Germany
  • Please see and review the updated WTP Component Teams. Pay attention to section on inactive committers.
  • Congratulations to Nitin on being named SSE component lead

WTP 1.5.5

WTP Release 1.5.5 Schedule

May 11-June 22 RDB Fixes
June 29 All Component Fixes
July 13 M Build
July 27 M Build
Aug 10 M Build
Aug 17 RC1
Aug 24 RC2
Aug 31 1.5.5 GA

  • Bug lists (WST,JST,JSF)
Invalid Targeted Defects <1.5.5 (0)
1.5.x Untargeted Blockers/Criticals (~0)
1.5.x Untriaged Bugs (~0)
1.5.5 Bugs for WTP PMC review and approval (~0)
1.5.5 Hot Bug Requests (~0)
1.5.5 Hot Bugs (~2)
1.5.5 Blockers, Criticals (~0)
1.5.5 Remaining Targeted Bugs (~11)
1.5.5 Total Bugs Fixed (~0)
1.5.x Resolved, Unverified (~15)
1.5.x Verified, Not closed (~0)

WTP 2.0

March 2007 - June 2007
Platform +1 WTP
RC1 May 18 May 23 May 25 1 PMC +1's
RC2 May 25 May 30 June 05 1 PMC +1's
RC3 June 08 June 13 June 14 2 PMC +1's
RC4 June 15 June 20 June 21 3 PMC +1's
Europa GA June 29 June 29 June 29
  • Europa To Do's
  • Ensure all plugin manifests have execution environments specified - David will verify this is done for RC0.
  • Use signed plugin jars - This is not a requirement anymore, are we still going to do for WTP 2.0?
  • Each component must run the eclipse copyright tool to ensure all files have a proper copyright. JSF done. J2EE no update.
  • Component Leads - Please update the exception section of the WTP 2.0 Europa Ramp Down Plan with the relevant info and bugzilla numbers for exceptions to M6 feature complete.
  • Updates to feature.xml's to pull in required dependencies on update site and for more fine grained EMF features. David to release for RC0.
  • WTP 2.0 API Delta - Component leads please provide a a summary of API changes between WTP 1.5 and 2.0 for your component. This is due by June 6th for the release review meeting.


  • April 6th - May 18th, WTP RC0
April 2007 - May 2007
Monday Tuesday Wednesday Thursday Friday
Function and Compatibility Tests
Defect Verifications
Mustfix defects
Defect Verifications
Mustfix defects
Defect Verifications
Status Call
Thumbs Up Test
Declare WTP 2.0 RC0

  • Build Status
JUnits all passing! One more respin tonight to get updates to feature.xml's but teams should start smoke testing.
Ready to declare? Please use the wiki status to declare readiness to declare RC0
Update site - David?
Website news update? Bob F will update and add new and noteworthy link when we declare tommorrow
  • Function and Compatibility Tests
You can store your tests plans here. You are encouraged to ask the community for help!
Remember to also be testing with many Europa components installed like BIRT or TPTP to ensure compatibility.
  • Bug Lists
Bugzilla Enhancements Targeted for 2.0 RC0 (~5)
2.0 Blockers/Criticals (~6)
All Resolved, Unverified by Severity (4 blockers, 7 criticals)
2.0 Remaining Targeted RC0 Defects (~85)


  • May 18th - May 25th, WTP RC1
May 2007
Monday Tuesday Wednesday Thursday Friday
Mustfix defects
Mustfix defects
Mustfix defects
Defect Verifications
Status Call
Thumbs Up Test
Declare WTP 2.0 RC1

  • PMC Review - One vote required, i.e. "tentative approval" on website
WTP 2.0 PMC Bugs for Approval Page
PMC members remember to use the flags instead of the +1 comment!
  • API Violations Review -
Raghu to investigate JSF ones. JSF numbers are significantly reduced. For remaining items, JSF will open bugs or API request bugs on dependencies.
Cannot underestimate the importance of this in the stability and quality of WTP as a platform. These numbers are embarrassingly high. Each component needs to really get someone focused each week on improving these numbers and opening API requests.
Action 1 = For any violation, open a bug to request API or fix code to not use internal discouraged access. An example is using images or labels from other plugins, these should be copied into your plugin. Also, using internal classes instead of the API interfaces.
Action 2 = If you do have a clean plugin of API violations/discourage access, switch prereq ranges wide so you can react to small version number changes without issue.
Action 3 = To be able to develop with discouraged access enabled, we need to update plugin's .classpath rules. Should we turn off defaults to expose all warnings to get a quicker resolution?
  • Bug Lists
2.0 Invalid Targeted Defects <RC1 (~85)
2.0 Remaining Targeted RC1 Defects (~39)
All Remaining 2.0 Targeted Enhancements (~13)
2.0 Hot Bug Requests (~1)
2.0 Hot Bugs (~0)
2.0 Untargeted Blockers/Criticals (~1)
2.0 Blockers/Criticals (~6)
2.0 Total JST, WST, JSF Bugs Fixed (~533)
2.0 Dali Total Bugs Fixed (~110)
2.0 Targeted Bugs (Graph)
All Remaining 2.0 Targeted Bugs (~177)

Bug Backlogs

All Untriaged WTP Bugs (Graph)
All Untriaged WTP Bugs (~88)
All WTP Verified, Not Closed Bugs (Graph)
All WTP Verified, Not Closed Bugs (3)
All WTP Resolved, Unverified Bugs (Graph)
All WTP Resolved, Unverified Bugs (525)
All WTP Defect Backlog (Graph)
All WTP Defect Backlog (2935)
All Resolved, Remind or Later (Graph)
All Resolved, Remind or Later (~58)
All Open WTP Bugs with Patches Attached (Graph)
All Open WTP Bugs with Patches Attached (~180)
All API Requests (9)

Working Groups

  • Java EE 5 - Servlet 2.5 and most scenarios working. Raghu reporting problems running UC1B and UC2B. Chuck to investigate.
JEE5 Test Scenarios
When opening related defects, add "JEE5-UC" in the Status Whiteboard

  • Website
Bob F - Pheonix enabled people pages looking good, working on tutorials and bugs, and new and noteworthy for rc0.

Other business?

David to investigate with webmaster possible issues with committing using platform M7 as a development environment. Kathy, Neil, and Raghu have all had some similar issues.

Teams Status and Focus for Coming Week

Server Component Team

Datatools (RDB, 1.5.x only)

XML/JSP Component Team

  • Working on limited "mustfix" defects
  • Defect (fix) verification
  • Updating tutorials (105989&181979) to match 2.0 UI
  • Reviewing performance tests
  • Ongoing triaging of incoming bug reports

Web Services Component Team

Java EE Component Team

You can now create servlets in Servlet 2.5 containers (Java EE 5 Web projects). The ModelProvider interface now allows modify()

Dali JPA

  • Completed last code items for RC0
  • Completed New and Note.



  • Investigating improving usage scans and test coverage reports
  • Running Performance and API tests


Known Issues
  • The baseline test needs to be rerun each week to eliminate false "hiccups" in performance.
Action Items
  • Improve the UI readability and cohesiveness of the output result pages
  • Improve the actual tests. Why do some take so long? Why do some results fluctuate? Why do some have 160% performance degradations? Are the tests even still valid?
  • Allow committers to reliably and efficiently run perfomance suites in the workspace before checking in code
  • Add JSF and JPA performance JUnits


  • This Week's Smoke Test Results
WTP 2.0 Smoke Results Page
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

Back to WTP Meeting Archives
Back to Web Tools Wiki Home

Back to the top