Skip to main content
Jump to: navigation, search


Revision as of 14:34, 19 July 2007 by (Talk | contribs)

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

WTP Development Status Meeting 2007-07-19


John L, Raghu S, Valentin B, Rob F, Carl A, Der Ping, Bob F, Nitin D, Larry D, Neil H, David W, Angel V


  • Congratulations to Carl Anderson becoming latest WTP Committer (Common and JEE Component Teams). (Paper work still in progress).
  • Eclipse will be moving to Bugzilla 3.0 which features an improved look and feel for bugs, as well as some new features.
  • Updates to the WTP Bug Workflow and Conventions. No more resolved remind or resolved later.
Bugs which need updated from the closed remind or later state
  • JPT and JSF please add target milestones for WTP 3.0.
  • We are aware of the committer build page issues and missing 1.5.5 builds. David is investigating 195692.
  • Chris Aniszczyk is organizing a community outreach Bug Day each month. Teams wishing to participate should sign up at this month's wiki page by the 26th.
Nitin is contact for JST and WST for first bug day and will post an announce to the newsgroup. Other committers should join as well. A key activity will be triaging bugs, i.e. making sure a bug has enough information to reproduce and possibly to attach a patch.
This is a great chance for WTP to start doing a better job of engaging and interacting with the open source community.

WTP 3.0

Requirements Review

  • For information on the iterative gathering and defining of requirements for this release, see the WTP 3.0 Requirements Wiki.
  • Web Tools Platform Release 3.0 Requirements - Defines the overall themes and structure for capturing component requirements.
  • Component Leads - Submit the features that you would like to see in this release by logging Enhancement Requests in Bugzilla. Then, update the document with the requirements that you would like to propose for this release. We will review these in next week's meeting.
  • July 31st - We will sign off on component lead and committer input and take forward for community review.


  • M1 Schedule?
July 2007 - August 2007
Monday Tuesday Wednesday Thursday Friday
Status Call
Smoke Test
Declare I Build
Status Call
Smoke Test
Declare I Build
Status Call
Smoke Test
Declare I Build
Status Call
Smoke Test
Declare I Build
Platform M1?
Start component lead change approval
Status Call
Smoke Test
Declare I Build
Write tests and produce FVT driver
FVT and Compatibility Tests
Defect Verifications
Mustfix defects
Defect Verifications
Mustfix defects
Defect Verifications
Status Call
Thumbs Up Test
Declare WTP 3.0 M1?

There will be some code work just to declare M1 as functional. For example, the platform has removed the tomcat plug-in and there are other plug-in prerequisite version ranges which will need to be updated.
  • M1 Themes - Each milestone we will have general, cross project themes. Open to suggestions like performance, accessibility, adopter readiness, etc.
Evaluate non-API use and ensure requests are open if our code cannot be changed.
Fix pre-req ranges where we are API clean.

  • Bug Lists
3.0 M1 Targeted Bugzilla Enhancements (~1)
All Remaining 3.0 Targeted Enhancements (~31)
3.0 M1 Remaining Targeted Bugs (~10)
3.0 M1 Hot Bug Requests (~2)
3.0 M1 Hot Bugs (~0)
3.0 M1 Blockers/Criticals (~0)
3.0 M1 JST, WST, JSF Bugs Fixed (~0)
3.0 M1 JPT Dali Bugs Fixed (~0)
3.0 Untargeted Blockers/Criticals (~0)
3.0 Resolved, Unverified Blockers/Criticals (~2) By Assignee
3.0 Total JST, WST, JSF Bugs Fixed (~4)
3.0 Total JPT Dali Bugs Fixed (~0)

WTP 1.5.5

WTP Release 1.5.5 Schedule - Note the change to the 1.5.5 schedule.

Remember 2 votes are required for PMC approval for 1.5.5.
July 27 M Build
Aug 10 RC1
Aug 17 RC2 (only if needed for blocking bugs or major regressions)
Aug 24
Aug 31 1.5.5 GA
  • If you fix a 1.5.5 bug, please open a separate 2.0.1 bug.
  • Build Status
JUnits - Failures in J2EE, JEM, and common. Please investigate ASAP.
No declared build this week for WTP 1.5.5.
  • Please note the 1.5.x releases are temporarily missing from our update site. Users can download the zips as a workaround.
  • Bug lists (WST,JST,JSF)
Invalid Targeted Defects <1.5.5 (~1)
1.5.x Untargeted Blockers/Criticals (~2)
1.5.x Untriaged Bugs (~9)
1.5.5 Bugs for WTP PMC review and approval (~1)
1.5.5 Hot Bug Requests (~0)
1.5.5 Hot Bugs (~1)
1.5.5 Blockers, Criticals (~3)
1.5.5 Remaining Targeted Bugs (~18)
1.5.5 Total Bugs Fixed (~37)
1.5.x Resolved, Unverified (~48)
1.5.x Verified, Not closed (~0)

WTP 2.0.1

  • Schedule
July 20 M Build
Aug 03 M Build
Aug 17 M Build
Aug 31 M Build
Sept 07 RC1 (PMC approval 2 votes)
Sept 14 RC2 (PMC approval 2 votes)
Sept 21 (if necessary, PMC approval 3 votes)
Sept 28 2.0.1 GA

  • Are we clear on branching policy and strategy? Apparently not.  :-) Result of discussion is we will table branching until we have the 3.0 plans in place. Note that JPT has already branched.
All the JST and WST stuff that was part of WTP 2.0 was tagged with a version of R2_0_0. Similarly, JSF and JPT with R1_0_0.
The releng project is branched to R2_0_maintenance, and JSF and JPT are branched to R1_0_maintenance. Please use these branches for your associated plug-ins, respectively.
David is working on creating a best practices and policies for branching as a start to incrementally make progress on effectively solving this problem.

Investigate not showing web service access errors, David?
Investigate adding section for known bugs and limitations from investigations into access warnings.
  • Build Status
JUnits - We have failures. We need to drop misbehaving tests so that declared builds are clean. Don't forget to open a bug against the removed test.
Please smoke test the latest 2.0.1 build to declare this week's M build on Friday.
  • Bug Lists
All Remaining 2.0.1 Targeted Bugs (~138)
2.0.1 Hot Bug Requests (~2)
2.0.1 Hot Bugs (~0)
2.0.1 Untargeted Blockers/Criticals (~0)
2.0.1 Blockers/Criticals (~5)
2.0.1 Total JST, WST, JSF Bugs Fixed (~23)
2.0.1 Dali Total Bugs Fixed (~13)
2.0.1 Resolved, Unverified Blockers/Criticals (~5) By Assignee

Bug Backlogs

All Untriaged WTP Bugs (Graph)
All Untriaged WTP Bugs (~127) 51 in J2EE components
All WTP Verified, Not Closed Bugs (Graph)
All WTP Verified, Not Closed Bugs (~0)
All WTP Resolved, Unverified Bugs (Graph)
All WTP Resolved, Unverified Bugs (~609)
All WTP Defect Backlog (Graph)
All WTP Defect Backlog (~3270)
All Resolved, Remind or Later (Graph)
All WTP Future Bugs (~42)
All Resolved, Remind or Later (~12)
All Open WTP Bugs with Patches Attached (Graph)
All Open WTP Bugs with Patches Attached (~232)
All API Requests (~9)

Working Groups

  • Java EE 5
JEE5 Test Scenarios

  • Website - Bob F
  • New newsfeed syndicated up on eclipse, and old links will redirect to the new RSS feed
  • Next will look at the download pages, David to help get started.
Maybe try and mimic the look of the EMF download page where they have a pheonix look and feel and have RSS like features
Cruise control does have an RSS feed to notify when build is complete, we could make more robust

Other business?

Teams Status and Focus for Coming Week

Server Component Team

Datatools (RDB, 1.5.x only)

XML/JSP Component Team

  • Working on fixes for 2.0.1 and 1.5.5.
  • Brainstorming 3.0 (no branching yet, though)
  • Ongoing triaging of incoming bug reports

Web Services Component Team

  • Working on fixes for 2.0.1 and 1.5.5.
  • Ongoing triaging of incoming bug reports.
  • Planning for WTP 3.0.

Java EE Component Team

Dali JPT

  • Updated 3.0 requirements doc
  • Fixing bugs for 2.0.1
  • Design/Requirements gathering for 3.0




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

API Violations Review

Visit latest build for current API violations.
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?


  • 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 3.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