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/September 02 2015"
m (Neon Planning) |
m (Neon Planning) |
||
Line 166: | Line 166: | ||
* See initial working draft of plan at [[Neon/Simultaneous_Release_Plan]]. | * See initial working draft of plan at [[Neon/Simultaneous_Release_Plan]]. | ||
* Continuing Discussion of if and how to change "yearly release"? | * Continuing Discussion of if and how to change "yearly release"? | ||
− | * - See [[SimRel/ChangingProcessAndTiming| "design" wiki page]], which acts as centralized place to document the main ideas and plans. | + | : * - See [[SimRel/ChangingProcessAndTiming| "design" wiki page]], which acts as centralized place to document the main ideas and plans. |
− | * - Rough scheduling alternatives ... what do we want to accomplish? | + | : * - Rough scheduling alternatives ... what do we want to accomplish? |
: * Current | : * Current | ||
Line 183: | Line 183: | ||
::: Advantages: predictable; each roughly 2, 6 week milestones | ::: Advantages: predictable; each roughly 2, 6 week milestones | ||
::: Disadvantage: arbitrary? | ::: Disadvantage: arbitrary? | ||
+ | ::: have to work around Thanksgiving holiday | ||
: * quick plus long | : * quick plus long | ||
Line 191: | Line 192: | ||
::: Disadvantage: does not easily map to 6 week milestones | ::: Disadvantage: does not easily map to 6 week milestones | ||
− | ::: still has as long period (5 months) of "no releases" | + | ::: still has as long period (5 months) of "no releases" |
+ | ::: but, that long period can be good for committers -- to have long period to focus on one stream. | ||
* Any new requirements? | * Any new requirements? | ||
− | : * In "signing section", I would like to add that jars that are already signed, | + | : * In "signing section", I would like to add that jars that are already signed, must not be re-signed. |
:: It messes up pack200 "conditioning" | :: It messes up pack200 "conditioning" | ||
Revision as of 21:46, 1 September 2015
Contents
Logistics
Meeting Title: | Planning Council Conference Call |
Date & Time: | Wednesday, September 2, 2015, 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
- ?
Previous meeting minutes
- Review previous meeting minutes if you'd like. That is, review them before meeting, but if questions or issues with previous minutes, this would be a good time to bring them up.
Mars Planning
- Any issues?
- How's "minor releases" in Mars.1 update going?
- - From the little I've seen, no radical change, but some change.
- - Some just being "more honest" about it (that's good).
- - Have seen the issue where changing "provisional API" to "API" is reason for the minor bump
- But, this can be "breaking" for anyone who was trying to use the provisional API (depending).
- Should we give any guidance in this area?
- - Have seen where "new features" would break translations.
- Should we give any guidance in this area?
Neon Planning
- See initial working draft of plan at Neon/Simultaneous_Release_Plan.
- Continuing Discussion of if and how to change "yearly release"?
- * - See "design" wiki page, which acts as centralized place to document the main ideas and plans.
- * - Rough scheduling alternatives ... what do we want to accomplish?
- * Current
- - June (3) September (5) February [(4) June]
- * Current plus one (equally spaced)
- - June (3) September (3) December (3) March [(3) June]
- Advantage; similar to current
- Disadvantage: hard and bad to release in (mid) December?
- * Equally spaced (based on May): (Similar to Doug's proposal?)
- - May, (3) August, (3) November, (3) February [(3) May]
- Advantages: predictable; each roughly 2, 6 week milestones
- Disadvantage: arbitrary?
- have to work around Thanksgiving holiday
- * quick plus long
- - June, (2) August, (5) January, (2) March [(3) June]
- Advantage: can have quick "service" after main releases,
- those features/projects that "just barely missed" main release points (June and January) won't have long to wait.
- Disadvantage: does not easily map to 6 week milestones
- still has as long period (5 months) of "no releases"
- but, that long period can be good for committers -- to have long period to focus on one stream.
- Any new requirements?
- * In "signing section", I would like to add that jars that are already signed, must not be re-signed.
- It messes up pack200 "conditioning"
New Business
- ?
Next Meeting
- October 7, 2015 - Regular First Wednesday Meeting
Reference
- 2013 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.