| [jdt-dev] Reviewing automated error reports |
| Hi jdt committers, a happy new year to everybody. I hope you had a great time. As some of you may have noticed on ide-dev, the next iteration of error reporter will not directly report problems to bugzilla anymore. Instead it will offer a lightweight web ui for managing (i.e., reviewing, requesting further information, and creating bugs in bugzilla) them. We’ll also offer daily reports on a per-project level which will summarize the latest changes to existing reports, which new reports arrived etc. With these emails and the web ui we hope to make it as convenient as possible for committers to review incoming error reports for their projects and to take necessary actions. Since the number of projects is continuously growing and I’m not able to review all incoming errors for all projects anymore, I’m kindly asking you whether (some of) you’d like to assist in reviewing error reports related to your project. Given the current statistics, I estimate that there will be around 10 reports per day to review. Is there anyone on the JDT team who would like to subscribe to these daily report emails and help to dispatch errors to the right people in your project - or is there a mailing list those reports should be sent to? Thank you, Marcel P.S.: An early prototype of the web ui is available at https://dev.eclipse.org/recommenders/committers/confess/#/ -- Codetrails GmbHThe knowledge transfer company Robert-Bosch-Str. 7, 64293 Darmstadt Managing Director: Dr. Marcel Bruch Handelsregister: Darmstadt HRB 91940 |