Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Planning Council/March 05 2014"
m (Next Meeting) |
(→Members and Attendees) |
||
Line 44: | Line 44: | ||
| Steffen Pingel | | Steffen Pingel | ||
| Mylyn (ALM) PMC | | Mylyn (ALM) PMC | ||
− | | | + | | D (Gunnar Wagenknecht) |
|- | |- | ||
| Brian Payton | | Brian Payton |
Latest revision as of 04:10, 6 March 2014
Contents
Logistics
Meeting Title: | Planning Council Conference Call |
Date & Time: | Wednesday, March 5, 2014, 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
- Reminder: deadlines and dates for Luna CQs, Reviews, etc.
Kepler SR2
- Any issues?
- There is one known, mysterious p2-update issue (discovered after 'release'): bug 427148
- I am surprised not hearing more complaints from users? (but, does seem "intermittent", somehow).
- I am surprised not many projects, apparently, tested "update" on Windows?
- Anyone hearing things questions/answers on newsgroups, etc.? Is that how "work around" is known?
Luna Planning
- M6 is soon!
- Plan for EclipseCon meeting (to be chaired by Ian)?
Progress on Action Items
- Luna+1 name: 'Mars' came back as "ok".
- Improved "aggregator examples/doc". (dw -- no progress).
- [Orbit plan (dw -- no formal progress)]
New Business
- Not "direct" Planning Council business, but Wayne asked us, as Eclipse Leaders, to look at two bugs:
- bug 429175 Eclipse flagged as malware in Chrome
- Can anyone reproduce? See similar things?
- bug 420511 No easy access to Eclipse version number/release name for bug tracker
- In general, Wayne's concern was that it's "too hard" for users to report bugs ... to pick from the scores of projects and hundreds of components, and feared some get "ignored" if in wrong place. One member pointed out its even hard for committers to know where to route! One suggestion was made that as a best practice, if a project gets a bug that "they don't know where it goes" that they move it to cross-project component, asking if anyone knows where it should go. The idea being that many (but not all) projects have people subscribed to cross-project component in-box.
Next Meeting
- EclipseCon "face-to-face" on Sunday (thanks Ian!) and "joint meeting" (Wayne did say he'd chair that one).
- April 2, 2014 - 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.