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.
Difference between revisions of "Planning Council/June 08 2016"
m |
m (/* Members and Attendees) |
||
Line 36: | Line 36: | ||
| Martin Lippert | | Martin Lippert | ||
| Cloud (PMC) | | Cloud (PMC) | ||
− | | | + | | Y |
|- | |- | ||
| Chris Aniszczyk | | Chris Aniszczyk | ||
Line 44: | Line 44: | ||
| Dani Megert | | Dani Megert | ||
| Eclipse (PMC) | | Eclipse (PMC) | ||
− | | | + | | Y |
|- | |- | ||
| Sam Davis | | Sam Davis | ||
| Mylyn (ALM) PMC | | Mylyn (ALM) PMC | ||
− | | | + | | Y |
|- | |- | ||
| Brian Payton | | Brian Payton | ||
Line 56: | Line 56: | ||
| Doug Schaefer | | Doug Schaefer | ||
| Tools (PMC) | | Tools (PMC) | ||
− | | | + | | Y |
|- | |- | ||
| Ian Bull | | Ian Bull | ||
| Rt (PMC) | | Rt (PMC) | ||
− | | | + | | Y |
|- | |- | ||
| Chuck Bridgham | | Chuck Bridgham | ||
Line 68: | Line 68: | ||
| Wayne Beaton | | Wayne Beaton | ||
| Eclipse Foundation (appointed) | | Eclipse Foundation (appointed) | ||
− | | | + | | R |
|- | |- | ||
| David Williams | | David Williams | ||
Line 80: | Line 80: | ||
| Marc Khouzam | | Marc Khouzam | ||
| Ericsson | | Ericsson | ||
− | | | + | | Y |
|- | |- | ||
| Alexander Nyssen | | Alexander Nyssen | ||
| itemis AG (Strategic Developer) | | itemis AG (Strategic Developer) | ||
− | | | + | | Y |
|- | |- | ||
− | | Nick Boldt | + | | Nick Boldt |
| Redhat (Strategic Developer) | | Redhat (Strategic Developer) | ||
− | | | + | | Y |
|- | |- | ||
| Remi Schnekenburger | | Remi Schnekenburger | ||
Line 104: | Line 104: | ||
| Stephan Merker | | Stephan Merker | ||
| SAP AG (Strategic Developer) | | SAP AG (Strategic Developer) | ||
− | | | + | | Y |
|- | |- | ||
| Markus Knauer | | Markus Knauer | ||
| EPP (appointed) | | EPP (appointed) | ||
− | | | + | | Y |
|- | |- | ||
| (has PMC rep; Dani Megert) | | (has PMC rep; Dani Megert) |
Revision as of 13:03, 8 June 2016
Contents
Logistics
Meeting Title: | Planning Council Conference Call |
Date & Time: | Wednesday, June 8, 2016, 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.)
|
Members and Attendees
|
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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
- Welcome Marc Khouzam as the Ericsson representative to Planning Council.
- Any others?
Previous meeting minutes
- Review previous meeting minutes if you'd like. That is, review them before the meeting, but if questions or issues with previous minutes, this would be a good time to bring them up.
Neon maintenance
- Dates (and RCs) for Neon.1 (etc.)
Oxygen Planning
- There has been a lot of discussion about "giving up release name" and using "date" instead.
ACTION ITEM: Wayne to discuss with Ian on how best to get more data from our community of users.
old (ongoing) stuff
- Release Policy vs. Release mechanics. This is being tracked in bug 483322.
- In M6 we changed to have (nearly) all features to be "root features.
- Now what? That is, can we "stop" adding "reference repositories" via feature p2.inf files?
- "Rolling release" issue.
- I have sometimes heard it suggested we allow more of a "continuous release". Is this something we should discuss? Should we have some long term planning for it? Such as, what would it take to accomplish that?
- This could be planned with or without the "beta stream" mechanisms sometimes discussed.
- Did not discuss much during this meeting, other than to note similarity to above issue.
- Should the ability to update from yearly release to yearly release be a 'requirement'?
- Impossible now, for Neon. Right? (for EPP Packages) Do we still need "streamless-URL" now? I am assuming "no".
- What would this take? (Such as features are never "just removed" but are replaced or transitioned?)
- Preferences, views, etc. have to "migrate" (if their ID changes).
- What testing would projects have to do?
- May become "defacto requirement" once bug 483786 is implemented.
- For Neon we will not have a "streamless" URL, since "won't work" for upgrading to Neon for the EPP packages.
New Business
- ?
Next Meeting
- August 3, 2016 - Regular First Wednesday Meeting -- We always skip July, since we "just shipped", and due to popular holidays.
- Other announcements:
Reference
- Draft Eclipse Project Branding Requirements (Wayne)