Bug Bingo for specific versions if the user specifies it

Bingo is a feature of the drupalorg module. I'm not sure that having that many bingo links is a good idea, but if they were to be added, it would be in there (which I mention just in case you are willing and able to provide code for this).

Moving this to drupal.org.

I think it may be a good default to have the patch bingo for core restricted to the current development release (e.g. 7.x these days), and for contrib, to the current stable release (6.x these days).

In the {project_issues} table, the "rid" field is the Release ID, which is the node ID (nid) of the release node representing the version that issue is currently associated with. If you just want to restrict to "6.x-*" then that's the "Drupal core compatibility" taxonomy term. So, for example, to find all issues that are currently assigned to a 6.x-* version, you'd need a query like this:

db_query("SELECT n.nid, n.title, prn.version FROM {node} n
  INNER JOIN {project_issues} pi ON n.nid = pi.nid
  INNER JOIN {project_release_nodes} prn ON pi.rid = prn.nid
  INNER JOIN {term_node} tn ON prn.nid = tn.nid
  INNER JOIN {term_data} td ON tn.tid = td.tid
  WHERE td.name = '%s' AND td.vid = %d",
  '6.x', _project_release_get_api_vid());

_project_release_get_api_vid() is a helper function from project_release.module that gives you the vocabulary ID (vid) used for these "API compatibility" terms...

Hope that helps,
-Derek

Here is a patch trying to only return recently created (less than 6 months) issues.
This patch incorporates changes from #483848: Core Bug Bingo brought me to an 'access denied' page.
I'm planning to add changes from #796214: bingo: Support support issues and a project-nid too.

I don't like the idea of only showing recently created issues. Many very old issues are still relevant (e.g. 8).

The idea here was focus on adding a version to the url that people could use to get issues for that version. Also, please don't combine some or all code from other issues. They should be reviewed and, if ready, marked RTBC so that they can be applied on their own.

Ok, I've reopened #483848: Core Bug Bingo brought me to an 'access denied' page and submitted a patch to review there (since it was close to the one I proposed earlier here).
@greggles, Thanks for your quick feedback and for helping me understand how and where to help.

This was also discussed in #1866436: Remove D6 from bug-bingo & patch-bingo results

Might be good to set one as a duplicate.