Skip to main content

WTP PMC Agenda/Minutes for May 13, 2008 Conference Call

WTP PMC Agenda/Minutes for May 13, 2008 Conference Call
Back

Call Info

Tollfree in the US: 877-421-0030
Alternate: 770-615-1247
Access code: 800388#
Full list of phone numbers

Call Time: 1500 UTC

Attendees

PMC Members

  • David Williams: Y
  • Naci Dai: N (Regrets)
  • Raghunathan Srinivasan: Y
  • Neil Hauge: Y
  • Tim deBoer: Y
  • Kaloyan Raev Y

Announcements and General Business

  • Amy Wu as committer in webservices sub-project?

    Confirmed

  • Java One Report (from Raghu)

    Some good action in 'spaces'. Java 6 hot topic. MyEclipse uses and masks us well. NetBeans doing well, especially for JSF.

Reports, Actions, Issues

Requirements: Raghu Srinivasan

Raghu has requested we discuss Requirements Document to help him "close it out" and begin next.

Note from meeting: Should create final copy before Release Review. Ask Project Leads to spend 20 minutes looking if any "completed" items should be mentioned (copied) under themes. If we have empty theme, should we remove? Or just say "we did no activity in this area".

We need Draft release plan, in standard format, for next years release by June (See see bug 215301).
Raghu to lead, and propose an alternative or two. Rumor has it that the June deadline was to have a standard format decided, and the "infrastructure" in place to roll them up into a single roadmap document. The "real" plan is expected by September. My understanding was there would be a new note to this effect to "project leads list", but haven't seen it yet.

Reference

Education: Naci Dai

meeting conflict till end of May

** Need status update

  • Phase 1, organize what we have, done by end January.
  • Phase 2, self guided new materials. some available by EclipseCon.
  • phase 3, shutdown .. scenarios
Notes:
Orgainizing "current" now, should be ready by EclipseCon.
Will be organized better for narrowing selection and sorting.
For now, the "database" will be one XML file, with various attributes/qualities to search and sort on.

Reference

Planning: David Williams

  • We may need another 2.0.2 patch -- and/or another release!, 2.0.3, to collect these "bad bugs". (I've asked Naci to get involved, but haven't heard anything yet.)
    • 201318 [hotbug] EAR Libraries container fails to initialize for 2.5 web project
    • 230256 hotbug_request] jst.jee JEEDeployableFactory refuses to load ejb3 module
  • Ganymede M7 ready (yesterday, today)
  • PMC Review
  • Beginning Review Materials
    • June 4th (materials due by 5/21) -- we'll need to work on via email with our final PMC review 5/20.
    • IP Log: third party code, list of committers, contributors, the newly required "other third party dependencies"
    • Coming up: do API summaries? List deprecated functions?
    • Need about files, etc., done by 5/15

Reference

Quality: Neil Hauge

  • Any remaining "automatically close since so old" work we should do now, before release?

    Note from meeting: We will skip any new auto processing for now (too late) and start-up after release.

Reference:

WTP User Experience Lead: Kaloyan Raev

  • Kaloyan still considering to do a walktrhough in a few weeks.
Notes:
  • Working on "use cases" document, for novice user. Should be ready for public review and comments in a few weeks.

References

Architecture: Tim deBoer

  • Tim will find out specific "advise to give developers (and auto-test teams)" to implement the WTP API policy (which tools/build reports to use).
Notes:
  • Recommended to restart the protected non-api scans.
  • Will not accept new data, for now, but if tooling could be improved to detect/remove additional (non-protected) data, then perhaps it'd be useful to show non-api use going down.
  • But, an update: Have discovered that current ones are nearly meaningless, since so much as changed, so scan's show us as "changing protected API", but it's not protected API any longer.
    • Concluded we should still run the scans, as sort of a "unit test" to see if any new, unexpected breakage. Run occasionally, that is, such as every milestone?
    • We'll need to tell developers to "make use of as best they can" since it includes lots of noise.
    • We may look at easy ways to reduce noise ... such as to "diff" with previous, or some particular reference report.
    • It was suggested at some point we may want to put the work back on adopters to sanitize their data, but, that might still require more work on our part to make sure no new usage data was added.

Reference

General business?

PMC Calendar

  • Eclipse World deadline has passed (though they sometimes accept late submissions). Who has submitted?

    Note from meeting: Raghu and Neil have submitted.

  • Eclipse European Summit

Back to meeting list.

Please send any additions or corrections to David Williams.

Back to the top