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 03 2010"
(→Next Meeting) |
(→ToDo Items) |
||
| Line 246: | Line 246: | ||
== ToDo Items == | == ToDo Items == | ||
| − | ( | + | * create (and update) [http://www.eclipse.org/projects/project-plan.php?projectid=helios 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 | + | * 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 == | == Other business == | ||
Revision as of 10:07, 3 March 2010
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 would not need an SR2, but after all decided they will need maintenance ... in March or so! ... apparently, this team has pattern of creating their service release shortly after the rest of us release?)
- PDT (PHP Tools) didn't have an SR2, but I saw one user on mailing list saying "he sure thought they needed one, based on important fixes made in Helios, that could be back ported ... its a long time to wait" (I've no idea if he was accurate ... just raising as an example that caught my attention).
- Potential for some Orbit Jars to not be consistent in some packages vs. others, if not everyone re-builds or re-packages. (Just one or two substantial changes, this time, but all others changed signatures).
- There were nearly equal numbers of projects that supplied service, vs. those that did not
- service released in SR2
- actf.build
- birt.build
- cdt.build
- dltk.build
- dsdp-tm.build
- dtp.build
- ecf.build
- eclipselink.build
- ep.build
- epp-udc.build
- equinox.build
- gef.build
- gmf.build
- jwt.build
- m2m-atl.build
- m2t-jet.build
- mylyn.build
- rap.build
- stp.build
- subversive.build
- swordfish.build
- tptp.build
- webtools.build
- no service released with SR2
- buckminster.build
- dsdp-tm.build
- emf-cdo.build
- emf-compare.build
- emf-emf.build
- emf-net4j.build
- emf-teneo.build
- emf-transaction.build
- emft-ecoretools.build
- emft-mint.build
- emft-mwe.build
- m2m-qvtoml.build
- m2t-xpand.build
- mat.build
- mdt-ocl.build
- mdt-uml2.build
- mdt-uml2tools.build
- mdt-xsd.build
- pdt.build
- riena.build
- tmf-xtext.build
- Any other concerns with SR2?
Good things:
- Maintained "old" content (SR1) in repository (in addition to new)
- Rolled out P2 artifacts before P2 metadata (instead of artifacts and metadata visible at same time)
- Any other positive things with SR2 to document?
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?
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
- EclispeCon 3/21 2:00 PM Pacific Time, in the Bayshore room of the Hyatt Santa Clara
- April 7, Wednesday, Noon Eastern Time.
Reference
Simultaneous Release Roles and Simultaneous Release Roles/EMO