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 "Eclipse/PMC"
< Eclipse
(→Meeting Minutes) |
|||
| Line 11: | Line 11: | ||
= Meeting Minutes = | = Meeting Minutes = | ||
| + | '''January 26, 2011:''' - | ||
| + | * Martin: Concerned about Eclipse 3.x quality, many regressions and not being addressed | ||
| + | ** {{bug|320329}} ThreadJob#waitForRun can spin when blockingJob is not RUNNING | ||
| + | *** '''Platform Runtime: Regression''' introduced in 3.6, can have severe Performance impact, reported 10-Jul, commenters unsure about approach to fix | ||
| + | ** {{bug|332840}} Wrong error about API change (Regression; works with 3.7M3) | ||
| + | *** '''API Tooling: Regression''' introduced in 3.7M4, reported 17-Dec, Olivier: "I'll take a look" but no response since | ||
| + | ** {{bug|332838}} Bogus potential null pointer access warning (regression; works with 3.6) | ||
| + | *** '''JDT: Regression''' introduced in 3.7M4, reported 17-Dec, Ayushman: "I'll investigate" but no response since | ||
| + | ** {{bug|335153}} Regression: p2 downloads are much slower due to picking remote artifacts even when a local file: URL is available | ||
| + | *** '''p2: Regression''' introduced in 3.6, reported 24-Jan, testcase + patch attached, response pending | ||
| + | ** {{bug|332507}} [regression] incomplete build path reported on o.e.rse.subsystem.shells.local | ||
| + | *** '''PDE UI: Regression''' introduced in 3.7M4, reported 14-Dec, initial traffic but no followup since 16-Dec | ||
| + | ** {{bug|313899}} [Progress] Every user-job causes a busy cursor to be shown for a minimum of 250ms | ||
| + | *** '''Platform UI''': Patch provided on 21-May, no response whatsoever from Platform UI | ||
| + | |||
| + | <hr/> | ||
''' January 19, 2011:''' - McQ, John, Jeff, Dani, Martin | ''' January 19, 2011:''' - McQ, John, Jeff, Dani, Martin | ||
* Jeff will be unavailable for meeting next 6-7 weeks | * Jeff will be unavailable for meeting next 6-7 weeks | ||
Revision as of 11:06, 26 January 2011
Documents
Some documents written and/or used by the PMC:
Meeting Schedule
The Eclipse Project PMC has a weekly phone meeting every wednesday at 10.30am EST.
Meeting Minutes
January 26, 2011: -
- Martin: Concerned about Eclipse 3.x quality, many regressions and not being addressed
- bug 320329 ThreadJob#waitForRun can spin when blockingJob is not RUNNING
- Platform Runtime: Regression introduced in 3.6, can have severe Performance impact, reported 10-Jul, commenters unsure about approach to fix
- bug 332840 Wrong error about API change (Regression; works with 3.7M3)
- API Tooling: Regression introduced in 3.7M4, reported 17-Dec, Olivier: "I'll take a look" but no response since
- bug 332838 Bogus potential null pointer access warning (regression; works with 3.6)
- JDT: Regression introduced in 3.7M4, reported 17-Dec, Ayushman: "I'll investigate" but no response since
- bug 335153 Regression: p2 downloads are much slower due to picking remote artifacts even when a local file: URL is available
- p2: Regression introduced in 3.6, reported 24-Jan, testcase + patch attached, response pending
- bug 332507 [regression] incomplete build path reported on o.e.rse.subsystem.shells.local
- PDE UI: Regression introduced in 3.7M4, reported 14-Dec, initial traffic but no followup since 16-Dec
- bug 313899 [Progress] Every user-job causes a busy cursor to be shown for a minimum of 250ms
- Platform UI: Patch provided on 21-May, no response whatsoever from Platform UI
- bug 320329 ThreadJob#waitForRun can spin when blockingJob is not RUNNING
January 19, 2011: - McQ, John, Jeff, Dani, Martin
- Jeff will be unavailable for meeting next 6-7 weeks
- John: How do we interpret "under the direction of the PMC" in Eclipse legal process?
- McQ: Not about approval, but about PMC being aware
- Jeff: Goal is to indicate "Working with an Eclipse mindset", ie in close collaboration with a committer ... contributor must be aware of IP due diligence guidelines from the beginning of evolution of the code. We want to avoid introducing IP leaks by accepting legacy code that was written before assuming an Eclipse mindset.
- McQ: This is about understanding the direction of Eclipse as a whole. Request a PMC +1 on the bug as work is being started. PMC should work with committer to ensure that contributor has been instructed about IP rules.
January 12, 2011: -
January 5, 2011: - McQ, John, Dani, Jeff, Martin
- Dani: Component Lead progress? - Portal still doesn't have the correct list of components