add invalid releases setting

Cool, thanks. No UI for it? Otherwise, looks good to my eyes, though I should probably test it a little before I call it RTBC. ;)

This patch doesn't change anything in hunmonk's patch but fixes a line right above the relevant part that currently uses a not-so-obvious syntax:

-          empty($rid) and form_set_error('project_info][rid', t('You have to specify a valid version.'));
+          if (empty($rid)) {
+            form_set_error('project_info][rid', t('You have to specify a valid version.'));
+          }

Oh, right, I also reviewed hunmonk's patch and it looks good to me. Can we put this up on project.drupal.org and remove the current hack (if it's on there right now) for testing? Testing this on a local test install isn't real easy.

Hrm, just tried this locally and we're never hitting the error message in this patch ("%version is not a valid version, please select a different value."). I tried it on d.o and the same is true there. :( This seems to have all changed with IFAC and I just never noticed. ;) Basically, once you rip the invalid value out of the list of available version drop down, when you load an issue with an invalid version, the version dropdown is pre-filled to just "none", and the only error you see if you try to post without changing it is "You have to specify a valid version.".

So, either:

A) we should get this working so that if we hit the no-version case, but the current value of the rid in the issue is invalid, we trigger the warning

or

B) the error message part of the patch is dead code and should be ripped out entirely.

I prefer (A) from a usability standpoint, but (B) is probably easier for the code. I'm torn.

I ended up implementing (A), committing, and deploying on d.o. See attached patch if you care.