I have filled out the survey, but I do want to stress one point that I think got missed in all the discussion…
Doing something about auto-censored stack frames is not entirely for third-party benefit. It is statistically improbably that all of the errors with third-party frames are caused by third-party code, yet all that I’ve seen collected for Sapphire are non-actionable in their current censored form. As such, we are losing on an opportunity to improve eclipse.org code as well as third-party code. Thanks, - Konstantin From: cross-project-issues-dev-boun...@eclipse.org [mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of Marcel Bruch Sent: Monday, August 03, 2015 2:49 AM To: Cross project issues Subject: Re: [cross-project-issues-dev] Error reporter and third-party code Am 31.07.2015 um 22:01 schrieb Konstantin Komissarchik <konstantin.komissarc...@oracle.com>: While we ponder broader process and infrastructure improvements To follow up on this part: So far only a few actively discussed this request. To me, and likely to others, it’s hard to say who really is interested in extending the scope of the error reporting and whether it’s worth taking this to the board of directors now. If you (and others on this list) have a couple of minutes, please cast your voice at this short form [1]. Thank you Marcel [1] https://docs.google.com/forms/d/1LtQ8QyMnQ1cD5XTXBdVgynGRaiKEMaUi9a0nxeRoumM/viewform
_______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
