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.
Planning Council/April 07 2010
< Planning Council
Revision as of 05:37, 3 March 2010 by David williams.acm.org (Talk | contribs) (New page: == Logistics == {| cellspacing="0" cellpadding="4" border="1" |- | Meeting Title: | '''Planning Council Conference Call''' |- | Date & Time: | Wednesday, March 03, 2010, at [http://...)
Contents
Logistics
| Meeting Title: | Planning Council Conference Call |
| Date & Time: | Wednesday, March 03, 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
Assessment of SR2
Potential (near?) negative impact on adopters:
- Some "late"
- Modeling EMF ?CDO? missed deadline
- DTP final zips late (sort of)?
- Not all projects had maintenance/rebuilds (do we need to explicitly "plan" for that?)
- EclipseLink (thought they wouldn't need an SR2, but after all decided they will need maintenance ... in March or so)
- PDT (PHP Tools) didn't have an SR2, but saw one user on mailing list saying "he sure thought they needed one, based on important fixes in Helios ... its a long time to wait" (I've no idea if he was accurate ... just raising as an example to be aware of).
- Potential for some Orbit Jars to not be consistent, if not everyone re-builds or re-packages. (one substantial one, this time, but others changed signatures).
- Other?
Good things:
- Maintained "old" content (SR1)
- Rolled out P2 artifacts before metadata (instead of artifacts and metadata visible at same time)
- Other?
Helios
- Common repository naming/structure bug 291637
- I want to recommend "guidelines" that may become "required" next year (but not for Helios)
- I want to recommend naming of /<project>/repository/<release>/[SRn | datetimestamp]/
- where 'project' is high level project (Top level? except Tools and Technology?)
- where 'release' is Yearly Release name ... only for those in yearly release.
- Also, do we agree that projects in release train can omit feature update URL, if they would like to (since the common one is built into platform). We need less "repository locations" clutter. Risk is it would be a little harder to provide off-cycle maintenance (users would need to add project location to their list).
Cross-Project Teams
Aggregation
Planning Council/Cross Project Teams/Aggregation
Previously planned meeting didn't happen ... and after some email exchanges, nothing concrete seemed needed.
Tracking progress and compliance
Review readiness of current version on Portal
Comments? Ok to move forward? Does anyone prefer Plan B or Plan C?
Other business
- Reminder: face-face EclipseCon meeting 2:00 to 3:00 (local time) on the Sunday before EclispeCon (3/21).
- TODO: I need to get/send room.
- Followed by "joint meeting" with other councils.
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).
- provide concrete instructions for (new) license-consistency requirement (John Arthorne).
Next Meeting
- EclispeCon 3/21 2:00 PM Pacific Time
- April 7, Wednesday, Noon Eastern Time.
Reference
Simultaneous Release Roles and Simultaneous Release Roles/EMO