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/August 7 2013"
(→Luna Planning) |
(→Luna Planning) |
||
Line 149: | Line 149: | ||
* Is there confusion/contradictions about "unreleased components in Sim. Rel. repo"? See {{bug|411977}}. | * Is there confusion/contradictions about "unreleased components in Sim. Rel. repo"? See {{bug|411977}}. | ||
− | * Are we "too lax" in versioning requirements? Especially for "maintenance"? See [http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg09221.html cross-project list posting]. [To be honest, I | + | * Are we "too lax" in versioning requirements? Especially for "maintenance"? See [http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg09221.html cross-project list posting]. [To be honest, I do not recall what specific situation this is about?] |
− | this is about?] | + | |
* I have started scheduling Luna milestones. I think first 4 or 5 will be similar to previous years. | * I have started scheduling Luna milestones. I think first 4 or 5 will be similar to previous years. | ||
Line 157: | Line 156: | ||
: * See [[Luna/Simultaneous_Release_Plan]]. | : * See [[Luna/Simultaneous_Release_Plan]]. | ||
− | * Can/should Planning Council say projects "should" contribute source to common repo? | + | * Can/should Planning Council say projects "should" contribute source to common repo? Or continue to "leave it up to projects" to decide? |
:: See thread around http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg09506.html | :: See thread around http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg09506.html | ||
:: Possibly {{bug|414262}} | :: Possibly {{bug|414262}} | ||
Line 164: | Line 163: | ||
* Doug also wants to discuss him taking over the aggregation builds and using Maven/Tycho. | * Doug also wants to discuss him taking over the aggregation builds and using Maven/Tycho. | ||
− | :: | + | :: The focus is still on projects providing OSGi bundles in p2 repos, right? No matter what technology they used to get there? |
+ | :: What type of "input" is required? | ||
+ | :: What type of "testing" is done that all is well formed and can be installed together? | ||
+ | :: In particular, how are "IDE" vs "runtime only" components treated separately? | ||
:: What are concrete advantages? | :: What are concrete advantages? | ||
Revision as of 00:57, 7 August 2013
Contents
Logistics
Meeting Title: | Planning Council Conference Call |
Date & Time: | Wednesday, August 07, 2013, at 1200 Noon Eastern |
Dial in: | (See Asterisk service for complete details on SIP, potential new numbers, phone mute commands, etc.)
Phone Numbers: (Check Asterisk/Numbers for more or current phone numbers.)
|
Members and Attendees
|
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Note: "Inactive" refers to Strategic Members or PMCs we have not heard from for a while, and have been unable to convince to participate. Those members can become active again at any time. Contact David Williams if questions.
Note: feel free to correct any errors/omissions in above attendance record.
Y = Yes, attended
N = No, did not
R = regrets sent ahead of time
D = delegated
X = not expected
Announcements
- New Member: Dani Megert is now the Eclipse PMC representative to the Planning Council. Thanks to John for years of service. Thanks Dani for volunteering to take his place.
Kepler Retrospective
- Propose to start in August, finish in September
Luna Planning
- Is there confusion/contradictions about "unreleased components in Sim. Rel. repo"? See bug 411977.
- Are we "too lax" in versioning requirements? Especially for "maintenance"? See cross-project list posting. [To be honest, I do not recall what specific situation this is about?]
- I have started scheduling Luna milestones. I think first 4 or 5 will be similar to previous years.
- * Appears that timing of EclipseCon in 2014 may effect how M6 is scheduled. It comes "the last week" of what would
normally be M6, instead of M6 finishing first.
- Can/should Planning Council say projects "should" contribute source to common repo? Or continue to "leave it up to projects" to decide?
- See thread around http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg09506.html
- Possibly bug 414262
- Discuss more frequent "(un?) coordinated releases" or updates to common repo or updates to EPP packages. (Doug, Ian).
- Doug also wants to discuss him taking over the aggregation builds and using Maven/Tycho.
- The focus is still on projects providing OSGi bundles in p2 repos, right? No matter what technology they used to get there?
- What type of "input" is required?
- What type of "testing" is done that all is well formed and can be installed together?
- In particular, how are "IDE" vs "runtime only" components treated separately?
- What are concrete advantages?
Next Meeting
- September 4, 2013 - Regular First Wednesday Meeting
Reference
- EclipseCon face-to-face follow-through action items. For original meeting notes, see Planning_Council/March_24_2013 and for discussion leading to action items, see Planning_Council/April_10_2013. For last status update, see Planning_Council/May_8_2013.