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/September 02 2015

< Planning Council
Revision as of 21:36, 1 September 2015 by David williams.acm.org (Talk | contribs) (Next Meeting)

Logistics

Meeting Title: Planning Council Conference Call
Date & Time: Wednesday, September 2, 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
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?
  • How's "minor releases" in Mars.1 update going?
- From the little I've seen, no radical change, but some change.
- Some just being "more honest" about it (that's good).
- Have seen the issue where changing "provisional API" to "API" is reason for the minor bump
But, this can be "breaking" for anyone who was trying to use the provisional API (depending).
Should we give any guidance in this area?
- Have seen where "new features" would break translations.
Should we give any guidance in this area?

Neon Planning

  • See initial working draft of plan at Neon/Simultaneous_Release_Plan.
  • Continuing Discussion of if and how to change "yearly release"?
  • - See "design" wiki page, which acts as centralized place to document the main ideas and plans.
  • - Rough scheduling alternatives ... what do we want to accomplish?
* Current
- June (3) September (5) February [(4) June]
* Current plus one (equally spaced)
- June (3) September (3) December (3) March [(3) June]
Advantage; similar to current
Disadvantage: hard and bad to release in (mid) December?
* Equally spaced (based on May):
- May, (3) August, (3) November, (3) February [(3) May]
Advantages: predictable; each roughly 2, 6 week milestones
Disadvantage: arbitrary?
* quick plus long
- June, (2) August, (5) January, (2) March [(3) June]
Advantage: can have quick "service" after main releases,
those features/projects that "just barely missed" main release points (June and January) won't have long to wait.
Disadvantage: does not easily map to 6 week milestones
still has as long period (5 months) of "no releases"
  • Any new requirements?
* In "signing section", I would like to add that jars that are already signed, should not be re-signed.
It messes up pack200 "conditioning"

New Business

  •  ?

Next Meeting

  • October 7, 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