Eclipse/PMC

Meeting Schedule

The Eclipse Project PMC has a weekly phone meeting every wednesday at 10.30am EST.

Meeting Minutes

Mar 4: - McQ, Steve, Jeff, Philippe, Martin

• Upgrade 3.4 -> 3.5
  • Will we be able to support this in p2?
    • Nope, needed hooks already in previous release (ie. needed them in 3.4 to be used by 3.5)
  • Problems include replacing the Eclipse .exe
  • Is this an important use case? There is no band width to solve this problem in 3.5
  • it's a good showcase for p2 technology
  • idea: put in the low level hooks for 3.5.1 and use them next time (ie. 3.5 -> 3.6)
  • Did Update Manager ever do this?
    • Jeff: It does not

• Deprecating Mac carbon?
  • Apple claims Cocoa is the future
  • 3.5 will be the last version of Eclipse where Carbon is under active development
    • But will maintain for 3.6 and 3.7
  • Q: Has Apple officially deprecated carbon?
    • No but they have down played it (ie. no 64-bit support for carbon)
  • Should there be an official deprecation policy for platforms?

Feb 25: - McQ, Steve, Martin, Philippe

• AC "committers should know" mail
  • Following external links McQ why not introduce some Javascript on the server that warns users automatically when they follow an external link?
  • Components to projects flattening (not on our plate at the time)
• Steve Target milestones for Eclipse project
• BZ patches to be flagged when they contain API
• N-builds broken over the weekend (again) - 3 weekends in a row - no people currently who are willing to work during the weekend
  • Hudson might help eventually, for now using e4 builds as the guinea pig
• UI Forms has no committers - opportunity for Community to become committer
  • migrate off (using internal browser instead)
  • no critical bugs, less than 125 interesting bugs
  • long-term future is e4 with css/styling and declarative ui
• Performance: No news (not yet while closing down API)
  • Philippe thinks that the performance milestone must be earlier since performance might touch on API. We're losing memory because rebasing
  • McQ - this cycle we had a performance run in M2, this year we're in a better position than last year

Feb 18: - no meeting

Feb 11:

Feb 4:

Jan 28:

• Java 6
  • move reference platform to Sun 6u11
    • problem(?): Sun added 3 new items added that are licensed LGPL or GPL
    • Martin added comment to bug 261724 to identify this issue
• ICU 4.0
  • we will stay with 4.0
• Deprecation Policy
  • still under discussion, bug 261544
• Use of internal provisional
  • seems to be some consensus about *not* requiring this, bug 261874
• JDT co-leadership
  • what is the process?
    • Jeff: vote in community; then propose to the PMC
    • Would like to get Dani Meghert involved.
    • Philippe will check development process documents
• Cocoa port
  • Looking good
  • Taking early access off and making it the "first" choice for Mac downloads
• Milestone progress / 3.4.2
  • Need to discuss M5 in arch call (should have done this last week)
  • Should always remind the team in the arch call of upcoming deadlines
  • Performance issues that need API to fix have to happen by M6
    • Teams should understand performance results (will be discussed in a couple of weeks)
• Re: Reference Platforms
  • Java6 on Solaris
    • Martin's company would like to support this
    • filed bug 262907 to discuss process and practices around reference platforms

Jan 21:

• How should we track meeting minutes topic - Wiki
• Provisional API conventions - Jeff working on bug 261874 for discussion at the AC
  • should there be a tag in the Javadoc (ie. "experimental")?
  • Jeff wants to keep the concerns "conventions" vs "Javadoc" separate
  • Jeff, "... Javadoc should not be generated for provisional ..."
  • Martin disagrees, "... need feedback and discussion for new API ..."
• What is the role of the PMC lead?
  • global view of components/processes
  • organize architecture call, ensure we are on track
  • spark conversations (ie. M5 is feature freeze)
• Reference platforms
  • we should choose JDK1.6, "update 11" rather than "update 4"
  • around "RC time", solidify the reference platform (it is the one we are testing on)

Jan 14:

• PMC component ownership x bugzilla pmc authorization