Ah. I get it.
Yeah, it is ready to be committed (at least I think it is). In terms of the "patch available" flag (which I appreciate you watching), I figure that's the flag that the assignee thinks it's ready to be committed. I can imagine adding patches that aren't ready for commit, in which case I wouldn't set the flag.
As far as doing the commit, I think on Hadoop, the committer just does the svn commit and resolves the Jira issue, w/o changing the assignee.
We don't have to do it that way, of course, but I do kinda like it that way. I figure if contributors (as opposed to committers) are the lead on any follow-up discussion, that's a good thing, in terms of load balancing?