Jump to: navigation, search

Difference between revisions of "WTP 2008-03-27"

(WTP 3.0 M6)
(Other business?)
Line 210: Line 210:
  
 
=== Other business? ===
 
=== Other business? ===
 
:* Meeting next week? Cancelling
 
  
 
:* David: we need to change how we generate our javadoc in the build -- project by project, or component by component.  
 
:* David: we need to change how we generate our javadoc in the build -- project by project, or component by component.  

Revision as of 17:15, 26 March 2008

WTP Development Status Meeting 2008-03-13

Attendees

Project Leads
Konstantin
Tim
Nitin
Kathy
Chuck
Naci
Raghu
Neil
David
Helen
Philippe
Committers
Bob
Carl
Dave
Phil
Kaloyan
Larry
Amy
Kate
Angel
Rob
Brad
Valentin
Friends
Nick

Announcements And Reports

  • Several teams announced version increments/API changes in this weeks I build, please update the New Help for Old Friends III page with the changes
  • Rob Frost leaving, thanks for all your hard work! Rob's work will be transitioned to Chuck's team.


Focus on Backlog and Quality metrics (Neil)

Current Focus Item
  • Options are
  • Target bug for a release or "future"
  • Mark as Invalid or Wont Fix
Upcoming Focus Item
Past Focus Items
  • 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.
  • Before July 1st, 2007 - 21
Where did they all go?
  • Minutes:
Neil: will focus on untargeted enhancements again after M7


Focus on Requirements Planning (Raghu)

Projects with no committed items: none
Please update status page
  • Please review untriaged enhancement requests
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

  • New patches are ready and sent for test => 222531
  • Recommend teams use update manager, and adding the "webtools/testUpdates" site, or use a policy file, as described at end of WTP Patches for Release 2.0.2
  • May have issues with install when the previous patch has already been installed, currently assessing
  • Currently 1 known "bad bugs" (critical, major, hotbugs) to be included in an offical post 202 patch
222531

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
  • Any issues with API/feature/UI freeze by Friday?
  • Builds
Build Breakages Board
3.0 Smoketest results


  • 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
  • Minutes:
David: Nitin contributed Junit changes to the current build
restarted cruisecontrol that was potentially causing the 28 of the JEM failures
Carl: Junit changes commented out for the build after the currently running one
David: Issue with moving up prereqs for JPT
Neil: platform changes that affects the JPT code, suspecting its an API change that's affecting JPT, hopefully just for this week, will figure out an alternative approach for next week's I build
Blockers/Criticals bugs
Neil: 220670: haven't heard back from the adopters in the new code, nothing that will be resolved right away, will look into it for M6
David: JSF bug 206514: looks like fix is already available, just didn't make it into this week's I build
Untargeted blockers/critical bugs
Larry: this is not a critical issue, will adjust severity
214888: Helen will send a note to Gerry on this one for update

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.

  • Minutes:
David: Generate db with platform test plugin, then things are okay, asked for the earlier build to be restored in the update site. Making progress on this, hopefully will have more report in 2 weeks

API Tools/Scans (Kaloyan)

Current ones will be ending soon. Kaloyan volunteered to explore the new Platform API tools, to make recommendations to WTP or build process.

Update 2008-03-06: 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.

Update 2008-03-13: No progress this week. I will try to catch API Tooling developers at EclipeCon next week. They also have a Long Talk on the event.

Other business?

  • 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

Source Editing

  • 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)

Server Tools

Web Services/WSDL

  1. Ongoing triage of incoming and existing bugs/RFEs.
  2. Fixing bugs and implementing RFEs.
  3. Planning for M6.

Java EE

Dali JPT

  • JPT 2.0
    • Released new Editor for persistence.xml
    • Completed Java to JPA project conversion support
    • Working on:
      • Project Explorer contribution
      • XML defaults and validation
      • EclipseLink support

JSF

  • Planning for M3
  • Property Editor prototype
  • JSPX support investigation
  • XHTML support investigation

releng

  • We will be changing the way we generate source features/plugins
See bug 132094 for details, implications, and links to more info.

References

  • Branching Strategy
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
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)


Bug Backlogs

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)


Back to WTP Meeting Archives