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/October 07 2015"
(Initial draft) |
(Neon Planning) |
||
| Line 158: | Line 158: | ||
* - Neon's 2016 Milestone Dates (M5, M6, M7, and RCs) | * - Neon's 2016 Milestone Dates (M5, M6, M7, and RCs) | ||
| + | :: See [[Neon/Simultaneous_Release_Plan#Schedule| Neon's Schedule]] | ||
| + | :: Similar to last year (EclipseCon is similar dates, as last year -- but on East Coast again! Yeah! :) | ||
| + | :: Do we all agree with those dates? (That is, can we declare them now official?) | ||
* - Neon's Update Release Dates | * - Neon's Update Release Dates | ||
: At meeting on [[../September_02_2015|last meeting]] it was decided to 3 update releases (instead of current 2), and have them approximately equally spaced: | : At meeting on [[../September_02_2015|last meeting]] it was decided to 3 update releases (instead of current 2), and have them approximately equally spaced: | ||
:: June (3) September (3) December (3) March [(3) June] | :: June (3) September (3) December (3) March [(3) June] | ||
| + | :: * I propose we plan the availability of Update Releases to be the same as the end of specific Neon+1 milestones. | ||
| + | :: - That would be M2, M4, and M6. (See Neon's schedule, for a rough idea of when Neon+1 milestones would be. | ||
| + | ::: - This has one obvious advantage: for projects that are essentially working on one stream only (such as fixes-only, especially for first Update Release), they can submit same content to the Update Release, and the Milestones stream. | ||
| + | ::: - Also, looking at schedule, the December "match up" seems a no brainer ... not much other time to do it? | ||
| + | ::: - M6 matching the last Update Release is nice, since gives "clear focus" for M7 and the end-game of Neon+1. | ||
| + | ::: - And Neon.1 matching M2 completes the rhythm. | ||
| + | ::: - From those "end dates" we would count backwards, to establish the same RC pattern we have now. | ||
| + | :::: - I've not looked closely, but believe the first "warmup" RC, would be same or near the previous Neon+1 milestone. (one quiet week, plus 3 one week RCs, plus 1 two week RC equals 6 weeks) [Is that good or bad? Do we still need that early warm up RC? (I'm inclined to say yes, if for nothing else, "new projects" joining train, and for those adding minor feature updates -- we still want a relatively early warm-up for them, similar to a update release milestone). | ||
| + | :* Can we say now we all agree with these dates? (I suggest "official vote" for next meeting, but if disagreement or concerns, speak up now!) | ||
| + | :* Has everyone had a chance to talk to their PMCs, Projects, or Strategic Members they represent? (Please do, we need, and want, complete buy-in from all stack holders -- that is, not so much what we dictate, as it is what they want ... or, at least tolerate). | ||
* Off-cycle "hot fix" releases/patches. | * Off-cycle "hot fix" releases/patches. | ||
Revision as of 04:51, 7 October 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
- Welcome Sam Davis as new (official) PC rep from Mylyn (ALM) PMC; and thanks to Steffen Pingel for his years of service.
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
- Mini Mars.1 retrospective:
Neon Planning
- See initial working draft of plan at Neon/Simultaneous_Release_Plan.
- - Neon's 2016 Milestone Dates (M5, M6, M7, and RCs)
- See Neon's Schedule
- Similar to last year (EclipseCon is similar dates, as last year -- but on East Coast again! Yeah! :)
- Do we all agree with those dates? (That is, can we declare them now official?)
- - Neon's Update Release Dates
- At meeting on last meeting it was decided to 3 update releases (instead of current 2), and have them approximately equally spaced:
- June (3) September (3) December (3) March [(3) June]
- * I propose we plan the availability of Update Releases to be the same as the end of specific Neon+1 milestones.
- - That would be M2, M4, and M6. (See Neon's schedule, for a rough idea of when Neon+1 milestones would be.
- - This has one obvious advantage: for projects that are essentially working on one stream only (such as fixes-only, especially for first Update Release), they can submit same content to the Update Release, and the Milestones stream.
- - Also, looking at schedule, the December "match up" seems a no brainer ... not much other time to do it?
- - M6 matching the last Update Release is nice, since gives "clear focus" for M7 and the end-game of Neon+1.
- - And Neon.1 matching M2 completes the rhythm.
- - From those "end dates" we would count backwards, to establish the same RC pattern we have now.
- - I've not looked closely, but believe the first "warmup" RC, would be same or near the previous Neon+1 milestone. (one quiet week, plus 3 one week RCs, plus 1 two week RC equals 6 weeks) [Is that good or bad? Do we still need that early warm up RC? (I'm inclined to say yes, if for nothing else, "new projects" joining train, and for those adding minor feature updates -- we still want a relatively early warm-up for them, similar to a update release milestone).
- Can we say now we all agree with these dates? (I suggest "official vote" for next meeting, but if disagreement or concerns, speak up now!)
- Has everyone had a chance to talk to their PMCs, Projects, or Strategic Members they represent? (Please do, we need, and want, complete buy-in from all stack holders -- that is, not so much what we dictate, as it is what they want ... or, at least tolerate).
- Off-cycle "hot fix" releases/patches.
- One proposal: have all features in EPP packages be "root features" and establish a procedure of adding new code to the Sim. Release repository "at any time" -- for "hot fixes" only ... after review/approval by Planning Council?
- AND, change p2? to "not allow" addition of reference repositories during feature installs.
- (Would likely have to be a "product preference" since some adopters may depend on that feature, but EPP could "set" the preference).
- Easy for me to say "change p2" :) but ... who would do the work?
- This "reference repositories issue" was a discussed as a concern at Architecture Council
- Apparently there have been cases of users getting "mixed" installs, because reference repositories are sometimes very broad. [I hope I've captured that issue correctly, I was not there, so please correct if I read it wrong.]
- Does Oomph solve this problem at all? Does it have a possible solution?
- - [ACTION ITEM from previous meeting] Wayne took as a "to do" item, to check with IP staff if a CQ deadline should be set for update releases.
- - Cons (probably not needed): there are few new ones, every one knows the limits
- - Pros (would be helpful): helps set expectations of committers and new contributors on how much can be done, by when.
- (Though, still varies a lot, if "all new" large contribution, vs. piggy back CQ)
New Business
- ?
Next Meeting
- November 4, 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.