Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Planning Council/January 06 2010"
(→Attendees) |
(→How to track) |
||
Line 162: | Line 162: | ||
:hierarchical categories (are more levels required?) | :hierarchical categories (are more levels required?) | ||
− | ==== | + | ====Tracking progress and compliance==== |
− | : | + | :[[Planning_Council/Cross_Project_Teams/Tracking]] |
==Long Term== | ==Long Term== |
Revision as of 04:40, 6 January 2010
Contents
Logistics
Meeting Title: | Planning Council Conference Call |
Date & Time: | Wednesday, January 06, 2010, at 1700 UTC / 0900 SFO / 1200 NYC / 1700 London / 1800 Berlin |
Dial-in: | For the call-in numbers, see the "Project Review" number on Foundation Portal page. |
Attendees
PMC (and Strategic) Reps
Strategic Reps
Appointed
|
Inactive
|
Galileo
Any SR2 issues? We will try RC1 as a rollup-warmup. RC2 will be true "release candidate".
Helios
- Thanks for the summary, John!
- John asks, What do we call this thing we do? "simultaneous release", "coordinated release", "annual release", "release train"?
- And ... who releases it? "The Eclipse Foundation", "The Eclipse Community", "The Eclipse Projects"?
- Discuss Helios/Participating_Projects document? Finalize?
Proposed (initial) Cross-Project Teams
Aggregation
Planning_Council/Cross_Project_Teams/Aggregation
Structure of Common Discovery Site
- users vs. extenders (minimum runtimes vs. SDKs)
- runtime targets vs. tools
- hierarchical categories (are more levels required?)
Tracking progress and compliance
Long Term
What needs to be done for e4?
ToDo Items
(volunteers welcome)
- create (and update) helios container plan (Wayne (re) volunteered)
- coordinate community input for next year's name (Oliver says last year this was started "shortly before EclipseCon" ... so, no rush).
Next Meeting
Reference
Simultaneous Release Roles and Simultaneous Release Roles/EMO