(In reply to Gabriele Svelto [:gsvelto] from comment #19) > Just one last note to be sure everybody is on the same page: Socorro being in maintenance mode doesn't mean it's going away, it means it's essentially feature-complete. We rely on Socorro for triaging and investigating crashes of native components and we relied on it for Fennec's Java crashes. I would suggest to keep submitting native crashes to Socorro to make them visible to engineering. At the moment there is no other reliable source for that and not having crashes in Socorro means we might not see them. Absolutely! I hope I was not implying that there was no value to Socorro. I just wanted to point out that there was nothing driving integrating it with Glean at the current time.
Bug 1575850 Comment 20 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Gabriele Svelto [:gsvelto] from comment #19) > Just one last note to be sure everybody is on the same page: Socorro being in maintenance mode doesn't mean it's going away, it means it's essentially feature-complete. We rely on Socorro for triaging and investigating crashes of native components and we relied on it for Fennec's Java crashes. I would suggest to keep submitting native crashes to Socorro to make them visible to engineering. At the moment there is no other reliable source for that and not having crashes in Socorro means we might not see them. Absolutely! I hope I was not implying that there was no value to Socorro. I just wanted to point out that there was nothing driving <edit>(or stopping)</edit> integrating it with Glean at the current time.