Skip to main content

WTP PMC Agenda/Minutes for September 27, 2011 Conference Call

WTP PMC Agenda/Minutes for September 27, 2011 Conference Call

Call Info

Toll free (in US and Canada): 888-426-6840
Access code: 5019600#
Caller pay alternative number: 215-861-6239
Full list of global access numbers

Call Time: 11:00 AM Eastern

Announcements and General Business

Congrats Kaloyan!

Now get some sleep...

Indigo SR1 delivered - Thanks

EPP Downloads for 3.7.1.

3.4 Release planning

Top-level plan

  • M2: Initial Planning document.
  • M3: Iterate/Review plans
  • M4: Final Plans due

Discuss API policy and bug 353775

Do we need to define facets as API - what attributes, behavior should be considered API? Possibly similar to plugin extension points where everything considered API. Let's discuss possible changes we can make to our policy documents for clarification

We may need to define our policy on API deprecation or altering API behavior in both the current and maintenance releases. Eclipse API Deprecation Policy

After some good discussion, we decided some clarification is needed for WTP's API policy, and Chuck will send an initial draft to the PMC list for further discussion. Neil pointed out a good statement(describing the "entire" API) from the platform is located here summary below: "Note that the API (Application Programming Interface) is the entire public programming surface of the framework, thus it includes not only Java classes, packages, and interfaces, but also extension points, file formats, generated meta-data, and even objects that are passed through to internal packages."

Discussion on Git adoption

Continue polling - re-evaluate by M4 - Should we put a stake in the ground mandating when we need to see some progress in educating our committers? - investigate a subproject that could "pilot" a git repo feeding into our overall PDE build - More discussion on CVS - GIT transition - should replace CVS feature for feature - Platform HAS put a stake in the ground.... CVS Retirement bug (Target: December 21, 2012)

Discussion on 4.2 adoption

Many small problems found - subtle changes in behavior - tracking with "wtp4x" in whiteboard. Tracking query

Dali - Possible mid-stream release

More details to come...

Other Business ... ? Progress from tracking bug

Progress moving WTP 3.4 builds "officially" to 4.2 platform as the default. Carl is finished promoting our Juno M2 build, and is 4.2 based. He has also changed the order and frequency of both 3.8 and 4.2 builds. EMF is fixing the problem with 3.8 based builds shortly after M2 is declared.

Future Agenda items

  • Discuss our model and assignments of "PMC Roles". Do they still make sense?


Back to meeting list.

Please send any additions or corrections to Chuck Bridgham.

Back to the top