Community
Participate
Working Groups
JDT core is lacking resources. There are 3 committers for JDT core which have to split their time to fix bugs in JDT and implement Java 9 support. See [1] for a recent summary. The FEEP funding would be well spent on 1) asking existing "spare time" committers to become full-time committers, or 2) hire another 1-2 developers (or companies that have resources) to support the core team to fix bugs (i.e., not adding new features or work on Java 9 support). FWIW, if no spare time committers can be found it might be easier to find developers that can work on jdt-ui and thus free existing resources there which, in turn, can help in jdt-core. [1] https://dev.eclipse.org/mhonarc/lists/jdt-dev/msg00816.html
(In reply to Marcel Bruch from comment #0) > JDT core is lacking resources. There are 3 committers for JDT core which > have to split their time to fix bugs in JDT and implement Java 9 support. > See [1] for a recent summary. Just wanted to share that we are currently ramping up a 4th committer.
Marcel is there any specific item that you want to see being improved in JDT?
-1 for me at the moment.
Created attachment 258130 [details] Distribution Error Reports per Project (In reply to Pascal Rapicault from comment #2) > Marcel is there any specific item that you want to see being improved in JDT? Similar arguments as in the platform bug. Platform and JDT jointly causing roughly 40% of all error reports (already excluding 3rd party traces, ui freezes, and traces other eclipse projects participate in). See the attached figure for details. Getting down this number should be the primary goal for FEEP. Since you won't find JDT committers who review and fix those issues, it needs additional resources. Building a "package of bugs" upfront is IMHO not possible b/c this would require a project lead to triage the items - and that' may already take 60% of the time. Thus, I'd give the EF the mandate to pay s/o just for fixing - with whatever payment model behind.
Note really an open way to change the scope/summary of this bug and let people vote on a completely different thing without notifying the community.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
This issue has been migrated to https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/215.
