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/January 06 2010"
(nominclature desision) |
(1/6) |
||
| Line 155: | Line 155: | ||
:*And ... who releases it? "The Eclipse Foundation", "The Eclipse Community", "The Eclipse Projects"? | :*And ... who releases it? "The Eclipse Foundation", "The Eclipse Community", "The Eclipse Projects"? | ||
| − | |||
| + | Resolved: best to use "Simultaneous Release" and "The Eclipse Foundation". (There was discussion that maybe "the PLanning Council" (but, no), and concerns that "the Community" was too inclusive, and "The Eclipse Projects", while correct :), is included as part of "The Eclipse Foundation". | ||
| + | <br> | ||
| + | <br> | ||
*Discuss [[Helios/Participating Projects]] document? Finalize?<br> | *Discuss [[Helios/Participating Projects]] document? Finalize?<br> | ||
| Line 164: | Line 166: | ||
:*Runtime | :*Runtime | ||
| − | ::Where's Reina? | + | ::Where's Reina? |
| + | ::''Tom to follow up with Reina and request exception if needed.''<br><br> | ||
:*Technology | :*Technology | ||
::egit and linux-distros have "expressed intent" but since not in build, require an [http://www.eclipse.org/helios/planning/EclipseSimultaneousRelease.php#pcExceptionProcess exception]. | ::egit and linux-distros have "expressed intent" but since not in build, require an [http://www.eclipse.org/helios/planning/EclipseSimultaneousRelease.php#pcExceptionProcess exception]. | ||
| + | ::''Wayne to follow up with these projects and request exception if appropriate. (He note 'egit' in particular was important to the "business" of Eclipse). ''<br><br><br> | ||
:*Modeling ... where to start? :) | :*Modeling ... where to start? :) | ||
::What is EEF? They (Cedric?!) just today are adding themselves to build. Appears a clear case where an [http://www.eclipse.org/helios/planning/EclipseSimultaneousRelease.php#pcExceptionProcess exception] is required first? | ::What is EEF? They (Cedric?!) just today are adding themselves to build. Appears a clear case where an [http://www.eclipse.org/helios/planning/EclipseSimultaneousRelease.php#pcExceptionProcess exception] is required first? | ||
| + | ::''Thanks to Cedric for reading agenda ahead of time and knowing he needs an exception. Him and Ed will discuss sending "formal" request to planning council list. ''<br>''Ed acknowledge projects such as GMF "are hard to contact" due to changes in companies and individuals status ... but, he will work on and resolve, since GMF is so important. ''<br><br> | ||
| + | |||
| + | *How is the "one row == one release" rule looking? | ||
| + | |||
| + | ''Ed agreed to fix up his part of table ... as well as make sure the subprojects do "roll up" with in the primary rows.'' | ||
| − | + | ''We still need rep for dsdp. '' | |
<br> | <br> | ||
| Line 214: | Line 223: | ||
|- | |- | ||
| Modeling | | Modeling | ||
| − | | | + | | 10? <br> |
|} | |} | ||
<br> | <br> | ||
| + | <br> | ||
=== Proposed (initial) Cross-Project Teams === | === Proposed (initial) Cross-Project Teams === | ||
Revision as of 14:18, 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".
Note: Remember we need to make SR2 "additive" with SR1 ... which
- requires some changes in builder to version categories
- provides opportunity for more testing?
Helios
- Remember to get your projects to submit CQ's by end of M5, and write in comments they are required for "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"?
Resolved: best to use "Simultaneous Release" and "The Eclipse Foundation". (There was discussion that maybe "the PLanning Council" (but, no), and concerns that "the Community" was too inclusive, and "The Eclipse Projects", while correct :), is included as part of "The Eclipse Foundation".
- Discuss Helios/Participating Projects document? Finalize?
- Runtime
- Where's Reina?
- Tom to follow up with Reina and request exception if needed.
- Technology
- egit and linux-distros have "expressed intent" but since not in build, require an exception.
- Wayne to follow up with these projects and request exception if appropriate. (He note 'egit' in particular was important to the "business" of Eclipse).
- Modeling ... where to start? :)
- What is EEF? They (Cedric?!) just today are adding themselves to build. Appears a clear case where an exception is required first?
- Thanks to Cedric for reading agenda ahead of time and knowing he needs an exception. Him and Ed will discuss sending "formal" request to planning council list.
Ed acknowledge projects such as GMF "are hard to contact" due to changes in companies and individuals status ... but, he will work on and resolve, since GMF is so important.
- How is the "one row == one release" rule looking?
Ed agreed to fix up his part of table ... as well as make sure the subprojects do "roll up" with in the primary rows.
We still need rep for dsdp.
| TLP | N Projects |
| BIRT | 1 |
| Datatools | 1 |
| DSDP | 3 ? |
| Eclipse | 1 |
| RT | 5 |
| SOA | 1 |
| TPTP | 1 |
| Web Tools | 1 |
| Tools | 6 |
| Technology | 6 |
| Modeling | 10? |
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