Am 24.10.2014 um 15:39 schrieb Lars Vogel :
> 2014-10-24 6:47 GMT+02:00 Eike Stepper :
>
> Two thoughts came up:
>
> 1) ... What about a simple Yes/No dialog prior to all the more complicated
> choices for those users who chose to opt in? Maybe together with a hint for
> where in the preferen
2014-10-24 6:47 GMT+02:00 Eike Stepper :
>
> Two thoughts came up:
>
> 1) ... What about a simple Yes/No dialog prior to all the more complicated
> choices for those users who chose to opt in? Maybe together with a hint for
> where in the preferences they can change their mind later.
>
+1 also a
Hi Marcel,
Thank you for this promising initiative!
Two thoughts came up:
1) It's too difficult (or too unintuitive) to opt out. Of course I'm crossing my fingers that many Eclipse users will
opt in, but for the remainder of the community it might be too disruptive to find the third choice in
st" of non-existing sites you find in the
> reports, in a common "cross-project" bug, or something? (In the past, when
> I open bugs on invalid ones, projects were very slow to fix, if they fixed
> at all.)
>
> Good luck,
>
>
>
>
>
> From: Marcel
Hi,
there is an updated documentation of the error reporting tool at [1]. It
contains a summary of the UI, guidelines how to use / leverage the system, and
how to help.
It also contains a set of sample bugzilla queries listing new yet unconfirmed
bugs of the last 7 days „by project“. These q
Hi Everybody,
great news.
On the platform.ui side, we have reworked our UI delay monitoring tool. The
origin tool I posted here on this mailing list, did not work correctly, as
we required new API from SWT. This has been implemented for Mars and we
have integrated the tooling into our latest Ecli
Thanks David.
> Don't be too quick to write all those off as "user error“.
True. Although useful, it's a different use case than I’m currently heading for
(finding problematic locations in code).
If we’d add this it would require some person reviewing those items and/or
needs code to be writte
thing? (In the past, when
I open bugs on invalid ones, projects were very slow to fix, if they fixed
at all.)
Good luck,
From: Marcel Bruch
To: Cross project issues ,
Date: 10/09/2014 01:36 PM
Subject: [cross-project-issues-dev] Updates on Automated Error
Reporting: Starte
Hi,
I’d like to give an update on the current status of the automated error
reporting started with Eclipse Mars M2 last week (and earlier iterations). The
error reporting tool is now part of Eclipse Mars M2 Committer Edition and
Modeling Package.
In the past ~4 weeks, we received 1500 error r
