Comment 13 for bug 695120

@Patrick: I'm sorry about your experience here. First off, let me apologize about the time to respond to your initial patch. We are a fully volunteer driven project and to say we are "understaffed" would be an understatement. Unfortunately sometimes things like this slip through the cracks and that really appears to be what happened in this case (evidenced by Kris apologizing after committing your original fix). Unfortunately, when it was committed just happened to fall between stable bugfix updates. The last bugfix update was unfortunately delayed by a few months due to an outstanding security vulnerability we were waiting for a fix on.

As for why you were assigned to this report, it was to ensure that we credited the person who submitted the fix for it. We're not saying you're always responsible for it, in most cases when a report is closed as Fix Released, that is the end of it. We have a policy for our project for contributors needing to submit 2 patches (which get accepted) to grant developer access, this is another reason we assign patch submitters to their reports (to track that). If you would like your assignment removed we can do that, but I can't promise it won't happen on future reports if you submit patches.