My only positive experience reporting bugs post early startup was with the chromium team, i get usually assigned to a dedicated reproducer that verifies and is reachable for helping them recreate in a matter of a few days. I had two experiences where bugs were taking less than a week from report to fix in canary.
That's impressive. I've only reported one bug to Chromium, years ago. It was a bug in their CSS engine and I included an HTML file with a full repro. It took them a few years to actually fix it since the person who was initially assigned it never bothered, eventually left Google, and nobody picked it back up for a while. But they did eventually fix it, so that's something, I suppose.
Edit: this comment elsewhere in the thread is closer to my experience: https://news.ycombinator.com/item?id=47523107 Certainly in my own stint at Google I saw the same thing--bugs below a certain priority level would just never get looked at.
I’ve had the worst experiences with Chromium. I’ve found multiple regressions in Chromium, tracked down regression points to a single commit, provided clear reproduction steps, shown that they do not reproduce with either Safari and Firefox or even older Chromium... And then the bugs were just ignored for years at this point. Sometimes some people played ping pong with the assignee field, before leaving it unassigned, and that’s it.
I don’t report any new Chromium regressions I find anymore.
