Hi Dani,
not sure I properly understand the question.
If you are asking wether I’ll still do a manual triaging: no, that’s not planned. If you fear we’d create bugs for every problem against JDT UI: no, that’s not planned. :-)
If you are asking whether it could be more fine-grained: yes, it could.
We work on an UI that allows committers to specify a mapping from package name prefixes (found in a stack trace) to bugzilla products and components. We’ll do some “magic” behind the scenes to determine which project and component to associate a problem with.
Let me know if that does not answer your question.
Marcel
Hi Marcel
Just to clarify: we would only get the
JDT bugs reported against JDT UI, i.e. those that you previously triaged
into Core, Debug, Text and UI?
Dani
From:
Marcel Bruch <marcel.bruch@xxxxxxxxxxxxxx>
To:
"Eclipse JDT general
developers list." <jdt-dev@xxxxxxxxxxx>
Date:
09.01.2015 09:48
Subject:
Re: [jdt-dev]
Reviewing automated error reports
Sent by:
jdt-dev-bounces@xxxxxxxxxxx
Hi Dani,
at the moment all errors are reported to recommenders.incubator
product and moved to an appropriate jdt component + version *manually*.
I’d like to remove that manual step. My proposal would be as follows:
We’ll move all “normal" problems (i.e, not ui freezes)
to JDT/UI component version 4.5 for now and leave it up to JDT team to
move it to the appropriate component and version. Over time we’ll add
logic that guesses the right components and versions based on the stack
trace and bundles on the class path.
Proper duplicate detection of UI freezes is yet not solved
and thus will stay in the external system for now.
If this approach is fine with you (short reply welcome),
we’ll implement this until M5.
Thanks,
Marcel
On 09 Jan 2015, at 08:54, Daniel Megert <daniel_megert@xxxxxxxxxx>
wrote:
Hi Marcel
Please just continue to report the bugs for JDT as you did before. The
UNCONFIRMED status easily allows us to separate them from normal/manual
bug reports.
Thanks,
Dani
From: Marcel
Bruch <marcel.bruch@xxxxxxxxxxxxxx>
To: "Eclipse
JDT general developers list." <jdt-dev@xxxxxxxxxxx>
Date: 09.01.2015
08:29
Subject: Re:
[jdt-dev] Reviewing automated error reports
Sent by: jdt-dev-bounces@xxxxxxxxxxx
Another option which has been discussed on cross-projects:
We may also directly report into your project’s bugzilla component. If
you specify a (default) component and version, we can redirect "problem
creation" events to this component. You may need to adjust component
and version later on, but with that approach you would at least not have
to monitor a second source of bug reports.
Please let me know what you think.
Thanks,
Marcel
On 08 Jan 2015, at 21:02, Marcel Bruch <marcel.bruch@xxxxxxxxxxxxxx>
wrote:
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 GmbH
The knowledge transfer company
Robert-Bosch-Str. 7, 64293 Darmstadt
Phone: +49-6151-276-7092
Mobile: +49-179-131-7721
http://www.codetrails.com/
Managing Director: Dr. Marcel Bruch
Handelsregister: Darmstadt HRB 91940
--
Codetrails GmbH
The knowledge transfer company
Robert-Bosch-Str. 7, 64293 Darmstadt
Phone: +49-6151-276-7092
Mobile: +49-179-131-7721
http://www.codetrails.com/
Managing Director: Dr. Marcel Bruch
Handelsregister: Darmstadt HRB 91940
_______________________________________________
jdt-dev mailing list
jdt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/jdt-dev
_______________________________________________
jdt-dev mailing list
jdt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/jdt-dev
--
Codetrails GmbH
The knowledge transfer company
Robert-Bosch-Str. 7, 64293 Darmstadt
Phone: +49-6151-276-7092
Mobile: +49-179-131-7721
http://www.codetrails.com/
Managing Director: Dr. Marcel Bruch
Handelsregister: Darmstadt HRB 91940
_______________________________________________
jdt-dev mailing list
jdt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/jdt-dev
_______________________________________________ jdt-dev mailing list jdt-dev@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/jdt-dev
-- Codetrails GmbH The knowledge transfer company Robert-Bosch-Str. 7, 64293 Darmstadt
Managing Director: Dr. Marcel Bruch
Handelsregister: Darmstadt HRB 91940
|
