Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Planning Council/August 05 2015

< Planning Council
Revision as of 12:58, 19 July 2015 by David williams.acm.org (Talk | contribs) (Mars Planning -- modified proposal)

Logistics

Meeting Title: Planning Council Conference Call
Date & Time: Wednesday, August 5, 2015, at 1200 Noon Eastern
Dial in: (See Asterisk service for complete details on SIP, potential new numbers, phone mute commands, etc.)

Phone Numbers: (Check Asterisk/Numbers for more or current phone numbers.)

For all phone lines: Participant conference extension: 710 then enter pin 35498
  • Ottawa (local call in Ottawa) 1-613-454-1403
  • North America (toll free) 1-866-569-4992
  • Germany (local call anywhere in Germany) +49-692-2224-6059
  • France (local call anywhere in France) +33-17-070-8535
  • UK (toll free) 0800-033-7806
  • Switzerland (local call anywhere in Switzerland) +41-44-580-2115
  • SIP clients:
call 710@asterisk.eclipse.org, then enter pin 35498.

Members and Attendees

PMC (and Strategic) Reps
John Arthorne (occasional) Cloud (PMC)
Chris Aniszczyk Technology (PMC)
Dani Megert Eclipse (PMC)
Steffen Pingel (Sam Davis) Mylyn (ALM) PMC
Brian Payton Datatools (PMC)
Doug Schaefer Tools (PMC)
Adrian Mos (Marc Dutoo ) SOA (PMC)
Ed Merks Modeling (PMC)
Ian Bull Rt (PMC)
Chuck Bridgham WTP (PMC)
Wayne Beaton Eclipse Foundation (appointed)
David Williams (appointed Chair)
Strategic Reps
Max Andersen? (and Nick Boldt) Redhat (Strategic Developer)
Remi Schnekenburger CEA List (Strategic Developer)
Cedric Brun OBEO (Strategic Developer)
Neil Hauge Oracle (Strategic Developer)
Stephan Merker SAP AG (Strategic Developer)
Markus Knauer Innoopract (Strategic Developer)
Rajeev Dayal Google (Strategic Developer)
(PMC rep) Actuate (Strategic Developer) X
(PMC rep) IBM (Strategic Developer) X
Inactive
[no name] CA Inc. (Strategic Consumer) X
[no name] Birt (PMC) X

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

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
D = delegated
X = not expected

Announcements

  •  ?

Previous meeting minutes

  • Review previous meeting minutes if you'd like. That is, review them before meeting, but if questions or issues with previous minutes, this would be a good time to bring them up.

Mars Planning

  • Any issues?
  • What to call September and February releases?
  • Propose to change name to "Mars 1" and "Mars 2" to better reflect the rules that have been in place for years (See Policy FAQ), and perhaps name change alone would help correct the mis-perception that "new things can be added only once per year". For some recent history detail, on how we end up with "just number", see mailing list thread on the topic.
  • This terminology applies only to "Simultaneous Release". Individual projects should still refer to their releases as accurately as possible (service release, or minor releas
- Largest impact would be to change "MarsSRn" type phrases to simply "Marsn" in the few places it is used.
- When generic words are needed, instead of numbers, the June Simultaneous Release will be call "the initial Simultaneous Release" and subsequent ones, when generic wording is needed will be called "subsequent release". For example, "Our project typically does XYZ in subsequent releases, not the initial release".
- The "Policy" (currently in Policy FAQ) will be "moved up" to the actual "plan" document. (Just as well move both items into the Plan, even if as footnotes.
> In general, "the policy" will emphasize that new projects can join in subsequent, as well as initial releases and projects can contribute "minor releases" as well as "service releases" ... it is up to the project. But, a) but be "backwards compatible" and b) almost never would be a "major release" -- would have to be a pure leaf component in Simultaneous Release, and have good reason to believe would not effect any adopters (hard to do, in practice), and would require "exception process" in Planning Council.
- We need to (also) add milestones for subsequent releases. I propose we have two milestones, M1 [not sure when, yet], and M2 become what we currently call the "warm-up RC". So, we would end up the 2 milestones, and 3 RC's. This is needed primarily for those new projects being added, or those adding large new features (But everyone should contribute "their latest", even if just working on service.
> New Projects or features would have to be by M2 [Or, should we be stricter, and say M1? -- at least, for Neon?]

Neon Planning

New Business

  •  ?

Next Meeting

  • September 5, 2015 - Regular First Wednesday Meeting

Reference

2013 EclipseCon face-to-face follow-through action items. For original meeting notes, see Planning_Council/March_24_2013 and for discussion leading to action items, see Planning_Council/April_10_2013. For last status update, see Planning_Council/May_8_2013.
Mars Wiki page
Planning Council Members
Simultaneous Release Roles and Simultaneous Release Roles/EMO

Back to the top