Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 474514

Summary:	How can AERI support Eclipse Platform better?
Product:	[Technology] EPP	Reporter:	Marcel Bruch <marcel.bruch>
Component:	Automated Error Reporting Client (AERI)	Assignee:	EPP Error Reports <error-reports-inbox>
Status:	CLOSED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	david_williams, Lars.Vogel, sptaszkiewicz
Version:	4.5.0
Target Milestone:	later
Hardware:	PC
OS:	Mac OS X
Whiteboard:
Bug Depends on:	465553, 466304, 469599, 473447, 474400, 474490, 474596, 475335, 476947
Bug Blocks:

Description Marcel Bruch

2015-08-07 13:42:52 EDT

Currently *all* error reports that could not be assigned to any other existing project are assigned to "Platform". This makes the Platform project the sink of all issues.

There is yet no distinction between "team", "resources", "swt" or any other component. This is mostly caused by the fact that I have no picture how the teams are structured inside the Eclipse, i.e., I don't know who is working and responsible for which plugins or package prefixes etc.

If it makes sense to create more fine-grained reports, I'm happy to provide more groups , specialized alerts and improve project guessing and duplicate detection for platform. 

Please let me know your requirements :-)

Comment 1 Szymon Ptaszkiewicz

2015-08-10 05:40:44 EDT

I added as dependencies a few bugs that already helped Platform.

Comment 2 Marcel Bruch

2016-05-24 07:04:52 EDT

closing due to inactivity. Most issues have been fixed except the fetch OS + version request which is tracked separately.