Revision as of 08:57, 16 August 2007 by Jlanuti.us.ibm.com
- 1 WTP Development Status Meeting 2007-08-16
- 2 Teams Status and Focus for Coming Week
- 3 References
WTP Development Status Meeting 2007-08-16
- Please review the Eclipse Platform 3.4 M1 new and noteworthy.
- The goal is to finish these by end of M1.
- Progress on Bug Backlog To Do's (Maybe we should add a date to the query to only show true backlog bugs?)
- Untargeted severity "Major" and higher bugs (7/26/07 - 256; Last week - 241; Currently ~237 )
- Untargeted severity "Major" and higher bugs opened before January 1st, 2007 (Last week - 167; Currently ~167 )
- Untargeted bugs with patches attached (7/26/07 - 134; Last week - 126; Currently ~126 )
- Untargeted bugs with patches attached opened before January 1st, 2007 (Last week - 85; Currently ~85 )
- Untargeted Enhancements Add "helpwanted" keyword if not in plan. (7/26/07 - 550; Last week - 500; Currently ~489 )
- Untargeted Enhancements opened before January 1st, 2007 (Last week - 374; Currently ~374 )
Still waiting on plans from Eclipse for the Ganymede release schedule, but anticipate us to follow their 6 week milestones by 2 weeks for the first 3 milestones.
- 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.
- Community Review
- Project/Component Leads: We have one action item. Please update the bugzilla for enhancement requests planned for 3.0 to include the keyword, plan. This will help in getting an accurate list of the work from the query on the Requirements Main page.
- The next step will be WTP 3.0 planning, and we expect this to be ongoing through end of August and middle of September with feedback from community taken into consideration.
- By ownership, this means you are responsible for sanity checking the current suite of tests, ensuring they are proper in timeliness and accuracy, and then making sure each week there are no regressions and that they are still running properly.
- Performance Test Owners
- wst-common - Konstantin
- wst-css - Nitin
- wst-html - Nitin
- wst-server - Angel
- wst-wsdl - Valentin
- wst-xml - Nitin
- wst-xsd - Valentin
- jst-j2ee - Carl
- jst-jsp - Nitin
- jst-server-tomcat - Angel
- jst-ws - Kelvin Cheung
- jst-jsf - Raghu - to be added in 3.0
- jpt - Neil - to be added in 3.0
- Latest Results
- WTP 2.0
- Known Issues
- Performance Test Bugs and Enhancements
- Improve the actual tests. Why do some take so long? Why do some results fluctuate? Why do some have drastic performance degradations? Are the tests even still valid?
- M1 Schedule?
July 2007 - August 2007 Monday Tuesday Wednesday Thursday Friday 13
EMF + GEF M1
Thumbs Up Test
Declare WTP 3.0 M1
- How are we looking in terms of delivering an M1?
- Changes in Internal API we use from the platform?
- Tomcat to Jetty changes?
- Plug-in dependency range updates?
- Tabbed properties view changes?
- Clean build?
- JUnits passing?
- New and Noteworthy? preview.
- Bug Lists
- 3.0 M1 Targeted Bugzilla Enhancements (~4)
- All Remaining 3.0 Targeted Enhancements (~130)
- 3.0 M1 Remaining Targeted Bugs (~13)
- 3.0 M1 Hot Bug Requests (~2)
- 3.0 M1 Hot Bugs (~1)
- 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 (~4) By Assignee
- 3.0 Total JST, WST, JSF Bugs Fixed (~15)
- 3.0 Total JPT Dali Bugs Fixed (~0)
- Remember 2 votes are required for PMC approval for 1.5.5.
- Aug 10 RC1
- Aug 17 RC2 (only if needed for blocking bugs or major regressions)
- Aug 24
- Aug 31 1.5.5 GA
- Aug 10 RC1
- If you fix a 1.5.5 bug, please open a separate 2.0.1 bug.
- Build Status
- Please smoke test the latest 1.5.5 build this week to declare RC2.
- Feature and Plug-in Version Updates?
- Test Plans and Results
- Bug lists (WST,JST,JSF)
- Invalid Targeted Defects <1.5.5 (~1)
- 1.5.x Untargeted Blockers/Criticals (~0)
- 1.5.x Untriaged Bugs (~2)
- 1.5.5 Bugs for WTP PMC review and approval (~0)
- 1.5.5 Hot Bug Requests (~0)
- 1.5.5 Hot Bugs (~0)
- 1.5.5 Blockers, Criticals (~3)
- 1.5.5 Remaining Targeted Bugs (~7)
- 1.5.5 Total Bugs Fixed (~79)
- All Bugs Fixed in 1.5.x Releases
- 1.5.x Resolved, Unverified (~62)
- 1.5.x Verified, Not closed (~0)
- Schedule - Details...
- Aug 17 M Build
- Aug 31 M Build
- Sept 07 RC1 (PMC approval 1 votes)
- Sept 14 RC2 (PMC approval 2 votes)
- Sept 21 (if necessary, PMC approval 3 votes)
- Sept 28 2.0.1 GA
- Aug 17 M Build
- Branching Strategy
- Please review and comment on the WTP How to: Branching Policy and Practices guide.
- Build Status
- Please smoke test the latest 2.0.1 build to declare this week's 2.0.1 M Build.
- Bug Lists
- All Remaining 2.0.1 Targeted Bugs (~155)
- 2.0.1 Hot Bug Requests (~2)
- 2.0.1 Hot Bugs (~1)
- 2.0.1 Bugs for PMC Approval (~0) Starts August 31st...
- 2.0.1 Untargeted Blockers/Criticals (~1)
- 2.0.1 Blockers/Criticals (~6)
- 2.0.1 Total JST, WST, JSF Bugs Fixed (~61)
- 2.0.1 Dali Total Bugs Fixed (~18)
- 2.0.1 Resolved, Unverified Blockers/Criticals (~7) By Assignee
- All Untriaged WTP Bugs (Graph)
- All Untriaged WTP Bugs (~120)
- 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 (~777)
- All WTP Defect Backlog (Graph)
- All WTP Defect Backlog (~3383)
- All WTP Future Bugs (~36)
- All Open WTP Bugs with Patches Attached (Graph)
- All Open WTP Bugs with Patches Attached (~238)
- All API Requests (~9)
- Bob F?
Teams Status and Focus for Coming Week
Server Component Team
Datatools (RDB, 1.5.x only)
XML/JSP Component Team
- Verifying 1.5.5 fixes while regression testing
- Working on fixes for 2.0.1
- Finally looking at our bug backlogs now that 1.5.5 is forcibly shutting down.
- Ongoing triaging of incoming bug reports
Web Services Component Team
Java EE Component Team
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
- Build Declaration Process Refined - See WTP Build Process and Procedures
- Information about process for milestone bugzilla line item planning has been added to the WTP Bugs, Workflow, and Conventions document.
- Adopter Migration Information for WTP 2.0 - Please add any details for your component.