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/March 21 2010"
(→Tracking progress and compliance) |
(→Helios) |
||
| Line 145: | Line 145: | ||
* We require a repository, and we require an optimized repository, but turns out "what is a repository" is not agreed to by everyone. See {{bug|306300}} and its predecessor {{bug|305939}}. Do we (Planning Council) agree on what a repository is? Is it fair to dictate that definition, for projects that want to participate in Simultaneous Release? | * We require a repository, and we require an optimized repository, but turns out "what is a repository" is not agreed to by everyone. See {{bug|306300}} and its predecessor {{bug|305939}}. Do we (Planning Council) agree on what a repository is? Is it fair to dictate that definition, for projects that want to participate in Simultaneous Release? | ||
| + | <!-- | ||
* Common repository naming/structure {{bug|291637}} [ongoing] | * Common repository naming/structure {{bug|291637}} [ongoing] | ||
| Line 156: | Line 157: | ||
''Notes from meeting: '' General agreement this was a good thing to do, and dw to write up for further review and/or (optional) adoption. | ''Notes from meeting: '' General agreement this was a good thing to do, and dw to write up for further review and/or (optional) adoption. | ||
| − | + | --> | |
=== Cross-Project Teams === | === Cross-Project Teams === | ||
| Line 165: | Line 166: | ||
A new Aggregator is (nearly) ready for testing. I hope to run the new one in parallel with old one. Currently, I'd be reluctant to change the "official" one, this late in the cycle, unless there's really good, important reasons to. | A new Aggregator is (nearly) ready for testing. I hope to run the new one in parallel with old one. Currently, I'd be reluctant to change the "official" one, this late in the cycle, unless there's really good, important reasons to. | ||
| + | <!-- | ||
[from previous meeting ... ] | [from previous meeting ... ] | ||
| Line 171: | Line 173: | ||
New question: Should we require projects to specify version numbers in .build file? | New question: Should we require projects to specify version numbers in .build file? | ||
::Technically, if omitted, then simply "highest" one is retrieved from repository. That can be good, easier, but a little less error checking and record of what was intended. | ::Technically, if omitted, then simply "highest" one is retrieved from repository. That can be good, easier, but a little less error checking and record of what was intended. | ||
| + | --> | ||
==== Tracking progress and compliance ==== | ==== Tracking progress and compliance ==== | ||
Revision as of 00:55, 18 March 2010
Contents
Logistics
| Meeting Title: | Planning Council Conference Call - EclispeCon F2F |
| Date & Time: | Wednesday, March 21, 2010, at UTC 2100 / 2:00 PM local time (Pacific, this time) |
| 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
|
Helios
- We require a repository, and we require an optimized repository, but turns out "what is a repository" is not agreed to by everyone. See bug 306300 and its predecessor bug 305939. Do we (Planning Council) agree on what a repository is? Is it fair to dictate that definition, for projects that want to participate in Simultaneous Release?
Cross-Project Teams
Aggregation
Planning Council/Cross Project Teams/Aggregation
A new Aggregator is (nearly) ready for testing. I hope to run the new one in parallel with old one. Currently, I'd be reluctant to change the "official" one, this late in the cycle, unless there's really good, important reasons to.
Tracking progress and compliance
How is your tracking going?
PMC Representatives: please be prepared to give brief (verbal) summary of the state of your projects. (such as, how many participating, anyone "late" on required or optional things like Accessibility checklists, which were due by end of M6?)
Seed list and process for next year's release name
- ?
- ?
ToDo Items
- create (and update) helios container plan (Wayne (re) volunteered)
- provide concrete instructions for (new) license-consistency requirement ... before M6? (John Arthorne).
- coordinate community input for next year's name (Oliver says last year this was started "shortly before EclipseCon" ... so now's the time!.
Other business
- Reminder: face-face EclipseCon meeting 2:00 to 3:00 (local time) on the Sunday before EclispeCon (3/21) in the Bayshore room of the Hyatt Santa Clara.
- Followed by "joint meeting" with other councils.
Next Meeting
- April 7, Wednesday, Noon Eastern Time.
Reference
Simultaneous Release Roles and Simultaneous Release Roles/EMO