Jump to: navigation, search

Planning Council/March 21 2010

< Planning Council
Revision as of 00:50, 18 March 2010 by David williams.acm.org (Talk | contribs) (EclipseCon meeting)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)


Meeting Title: Planning Council Conference Call - EclispeCon F2F
Date & Time: Wednesday, March 21, 2010, at UTC 2100 / 2:00 PM local time (Pacific, this time)
Dial-in: For the call-in numbers, see the "Project Review" number on Foundation Portal page.


PMC (and Strategic) Reps

Chris Aniszczyk Technology (PMC)
John Arthorne Eclipse (PMC)
Oliver Cole Tptp (PMC)
Brian Payton Datatools (PMC)
Doug Gaff ??? Dsdp (PMC)
Anthony Hunter Tools (PMC)
Oisin Hurley Stp (PMC)
Ed Merks Modeling (PMC)
Thomas Watson Rt (PMC)
David Williams WTP (PMC) (appointed Chair)
Gary Xue Birt (PMC)

Strategic Reps

Cedric Brun OBEO (Strategic Developer)
Stefan Daume Cloudsmith Inc.(Strategic Developer)
Neil Hauge Oracle (Strategic Developer)
Kaloyan Raev SAP AG (Strategic Developer)
Markus Knauer Innoopract (Strategic Developer)
Christian Kurzke Motorola (Strategic Developer)


Wayne Beaton Eclipse Foundation (appointed)
Mike Milinkovich Eclipse Foundation (appointed)

Note: feel free to correct any errors/omissions in above attendance record.
Y = Yes, attended
N = No, did not
R = regrets sent ahead of time


 ? Nokia (Strategic Developer) X
 ? CA Inc. (Strategic Consumer) X
 ? brox IT-Solutions GmbH (Strategic Developer) X

Note: "Inactive" refers to Strategic Members we have not heard from in a year or so, and have been unable to convince to participate. Those members can become active again at any time. Contact David Williams if questions.


  • We require a repository, and we require an optimized repository, but turns out "what is a repository" is not agreed to by everyone. See bug 306300 and its predecessor bug 305939. Do we (Planning Council) agree on what a repository is? Is it fair to dictate that definition, for projects that want to participate in Simultaneous Release?
  • Common repository naming/structure bug 291637 [ongoing]
I want to recommend "guidelines" that may become "required" next year (but not for Helios) but some, such as webtools, may move to it this release:
... structure of .../<project>/repository/<release>/[SRn | datetimestamp]/
... naming in feature URL would be (only) .../<project>/repository/<release>/
where 'project' is high level project (Top level? except Tools and Technology? ... or request even Tools and Technology to have central one, or at least part of name and/or structure?
Such as /tools/gef/repository/helios/ ?
where 'release' is Yearly Release Name (e.g. 'helios') ... only for those in yearly release. Others would need to use some version number. (reserving yearly release name, for only those in yearly release).
  • Also, do we agree that projects in release train can omit feature update URL? if they would like to? (since the common release repository URL is built into platform). We need less "repository locations" clutter. Risk is it would be a little harder to provide off-cycle maintenance (users would need to add project location to their list) for those projects deciding not to provide their own URL. They would, still, need to provide their own repository (since that's where central one is created from) just not name it in the feature.xml.

Notes from meeting: General agreement this was a good thing to do, and dw to write up for further review and/or (optional) adoption.

Cross-Project Teams


Planning Council/Cross Project Teams/Aggregation

A new Aggregator is (nearly) ready for testing. I hope to run the new one in parallel with old one. Currently, I'd be reluctant to change the "official" one, this late in the cycle, unless there's really good, important reasons to.

[from previous meeting ... ]

We will encourage people to test Galileo to Helios upgrade, but not do anything to enable that to be "automatic". See or comment in bug bug 303583.

New question: Should we require projects to specify version numbers in .build file?

Technically, if omitted, then simply "highest" one is retrieved from repository. That can be good, easier, but a little less error checking and record of what was intended.

Tracking progress and compliance

Planning Council/Cross Project Teams/Tracking

How is your tracking going?

Seed list and process for next year's release name

  •  ?
  •  ?

ToDo Items

  • provide concrete instructions for (new) license-consistency requirement ... before M6? (John Arthorne).
  • coordinate community input for next year's name (Oliver says last year this was started "shortly before EclipseCon" ... so now's the time!.

Other business

  • Reminder: face-face EclipseCon meeting 2:00 to 3:00 (local time) on the Sunday before EclispeCon (3/21) in the Bayshore room of the Hyatt Santa Clara.
  • Followed by "joint meeting" with other councils.

Next Meeting

April 7, Wednesday, Noon Eastern Time.


Helios Simultaneous Release

Planning Council Members

Simultaneous Release Roles and Simultaneous Release Roles/EMO