before we push too hard the bug should at least have a description on
what effects it has to users and how to reproduce.
Also, please create jira on our side to track it if its this critical.
/max
Hey Gorkem:
Wanted to point you to
https://bugs.eclipse.org/bugs/show_bug.cgi?id=437351
I've currently marked it as a hotbug, but I suspect this isn't correct
since technically we have committers on the project (you).
If you can assist at pushing this through, I'd be most grateful. I
think you're supposed to mark it as p1, since you're a committer.
The patch suggestion (adding a synchronized) is safe, and, is clearly
the right solution. It's an internal private method, and should in no
way NOT be synchronized, so I think this should be an uncontroversial
fix for you.
Can you do the legwork to get the approvals we need? We're short on
time. This race condition is nasty.
- Rob