- 1 WTP Development Status Meeting 2008-03-13
- 1.1 Attendees
- 1.2 Announcements And Reports
- 1.3 Post WTP 2.0.2
- 1.4 WTP 3.0 M6
- 1.5 Performance Focus (Kaloyan)
- 1.6 API Tools/Scans
- 1.7 Other business?
- 2 Teams Status and Focus for Coming Week
- 3 References
WTP Development Status Meeting 2008-03-13
Announcements And Reports
EclipseCon WTP Committers BOF, Monday evening.
Focus on Backlog and Quality metrics (Neil)
Current Focus Item
- Untargeted bugs with patches attached opened before January 1st, 2008 (Last week - 44; Currently ~ 24)
- Options are
- Target bug for a release or "future"
- Mark as Invalid or Wont Fix
- Minutes: Note sent to Kate Price (Documentation) (current leader at 6 ... though seveal 5s too)
Upcoming Focus Item
Past Focus Items
- Untargeted Enhancements opened before January 1st, 2007 (Last week - 62; Currently ~ 58)
- Before July 1st, 2007 - 109
- Options are
- Invalid - Enhancement does not fit with the scope of the project or is already implemented.
- helpwanted keyword - This is a valid request, but due to committer resources and other priorities, outside help will be needed to make this happen.
- Future - I would use this in conjunction with the helpwanted keyword. I use this for legitimate requests that are important but will not make any planned release, but likely will make a future release.
- Untargeted severity "Major" and higher bugs opened before January 1st, 2007 (Last week - 2; Currently ~ 0)
- Before July 1st, 2007 - 21
Focus on Requirements Planning (Raghu)
- Review and Update the WTP 3.0 Plan by April 7
- Projects with no committed items: none
- Please update status page
- Please review untriaged enhancement requests
- Reminder: Any feature work that slips past M6 needs PMC review, and needs to be explicitly listed on ramp down page. (Before the end of M6!)
- David will update docs and send reminder note.
- Document updated to clarify policy. See WTP 3.0 Ramp down Plan for Ganymede
Post WTP 2.0.2
- Patches are ready to test. We'd like all teams to give brief smoke test with all patches applied, just to confirm no obvious side effects. Those teams that contributed the fixes should test to confirm their fixes are in the build correctly.
- Plan is to put on official /webtools/updates on Friday, as soon as smoke tests complete.
- Recommend teams use update manager, adding the "webtools/testUpdates" site, or use a policy file, as described at end of WTP Patches for Release 2.0.2
- Currently 3 known "bad bugs" (critical, major, hotbugs) to be included in an offical post 202 patch
- The PMC recommends we produce official patches, regression test, and release those to update site
WTP 3.0 M6
- our +2 date: Monday, April 7 2008
- Final Code released by March 28th
- Plan 02/18 - 02/22
- Development 02/25 - 03/28
- Test 03/31 - 04/04
- M6: API, feature, UI freeze
- Bug Lists
- 3.0 Invalid Targeted Bugs (~3)
- 3.0 M6 Targeted Bugzilla Enhancements (~31)
- All Remaining 3.0 Targeted Enhancements (~156)
- 3.0 M6 Remaining Targeted Bugs (~154)
- 3.0 M6 Hot Bug Requests (~0)
- 3.0 M6 Hot Bugs (~0)
- 3.0 M6 Blockers/Criticals (~1)
- 3.0 M6 JST, WST, JSF Bugs Fixed (~99)
- 3.0 M6 JPT Dali Bugs Fixed (~36)
- 3.0 Untargeted Blockers/Criticals (~2)
- 3.0 Resolved, Unverified Blockers/Criticals (~28) By Assignee
Performance Focus (Kaloyan)
Some (possible) progress on debugging the problem with running the tests. Seems related to org.eclipse.test.performance
We'll begin having weekly performance section to review tests and test results.
Update 2008-03-06: We have identified that changes made in bug 201469 could be a potential reason for the Derby error:
ERROR 42Y07: Schema 'GUEST' does not exist
The changes in the bug are about improving performance, but they also affect the org.eclipse.test.internal.performance.db.DB class and if we compare between revisions 1.68 and 1.70 we could see that the changes deal with some user and password settings. Now it is not clear what should be changed in the WTP perf tests setup to comply with this change. May be setting some user and password for Derby?!
Update 2008-03-13: We have found an interesting article about Derby that seems to explain the problem. There it is explained that if the database is accessed without authentication, then the default database schema is APP. This is our case before the changes of bug 201469. But, if authentication is used, then the default schema becomes the username. After the changes of bug 201469 all access to the DB is done through the default user Guest. The DB driver tries to find the tables in schema GUEST instead of in schema APP. This explains the Error message above.
We see the best solution is to rename the schema in our Derby database from APP to GUEST for builds after bug 201469. We are now investigating how to do this.
Current ones will be ending soon. Kaloyan volunteered to explore the new Platform API tools, to make recommendations to WTP or build process.
Kaloyan: I have started exploring and evaluating the Api Tooling project. It is planned to become part of Eclipse 3.4 by the end of M6. Now it is available only by checking it out from CVS.
Project overview: http://wiki.eclipse.org/PDE_UI_Incubator_ApiTools
The Api Tooling supports profiles. I need to check if this can correspond to our adopter usage reports.
There are also Batch mode tools: Binary Compatibility Reporting and API Usage Reporting, but I am still in progress to find out how to run them.
- Meeting next week?
- David: we need to change how we generate our javadoc in the build -- project by project, or component by component.
- Tim has volunteered to do something for the server project, and recommend to others (might check with Nick Bolt on this).
Teams Status and Focus for Coming Week
- Ongoing triaging of incoming bug reports
- Working on updating bug backlogs
- Working on 3.0 requirement for more configurable XML and HTML formatting (95091,194698)
- Ongoing triage of incoming and existing bugs/RFEs.
- Fixing bugs and implementing RFEs.
- Planning for M6.
- JPT 2.0
- New model/UI code is in last weeks I-Build
- Working on:
- Persistence.xml editor
- Java to JPA project conversion
- EclipseLink support
- Planning for M3
- Property Editor prototype
- JSPX support investigation
- XHTML support investigation
- We will be changing the way we generate source features/plugins
- See bug 132094 for details, implications, and links to more info.
- Branching Strategy
- Please review and comment on the WTP How to: Branching Policy and Practices guide.
- In general, the minimum is if you branch a plug-in to branch all the plug-ins in the corresponding map file. It is fine to branch everything if you choose as well. We may need to reorganize map files slightly and we can investigate that on a case by case basis. This is intended to be a living document and open to evolutions and improvements.
- 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.
- 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.
- 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
- All Untriaged WTP Bugs (Graph)
- All Untriaged WTP Bugs (~227)
- All WTP Verified, Not Closed Bugs (Graph)
- All WTP Verified, Not Closed Bugs (~159)
- All WTP Resolved, Unverified Bugs (Graph)
- All WTP Resolved, Unverified Bugs (~1532)
- All WTP Defect Backlog (Graph)
- All WTP Defect Backlog (~3168)
- All WTP Future Bugs (~166)
- All Open WTP Bugs with Patches Attached (Graph)
- All Open WTP Bugs with Patches Attached (~229)
- All API Requests (~9)