no CVS directory validation for "Administer projects" users -- need better description?

lemme guess, you made your branch and tag *before* you made the project node, right? the {cvs_tags} table was empty for this project, and i think the only way that can possibly happen now is if you add branches/tags when there's no project node at all. i should document this.

meanwhile, i manually added the records you need, so you should be all set.
-derek

http://drupal.org/handbook/cvs/quickstart#branch-tag already started with:
"Note: Before you can branch/tag a module, it needs to have a project created."

however, for good measure, i added a blurb to both:
http://drupal.org/handbook/cvs/releases and http://drupal.org/node/100748

also added a note to http://drupal.org/node/7765
if there are any other places someone might need to know this, please just edit accordingly. thanks.

Nope, I did-

1. Add to cvs
2. Create project
3. Create branch and tag
4. Attempt to create releases

hehe, i looked more closely, and discovered this tale of woe:

• http://drupal.org/node/127205/edit contains only "/job_queue/" for the "CVS directory" field.
• there's a ton of validation for this field, to make sure it should be "/modules/job_queue/" for module projects
• the description of this field doesn't actually say all the rules that should be followed, and relies on the validation to report the errors.
• all of the valiation is disabled for people with "Administer projects" permission (since in some cases, we wanted to ignore this validation, and people with "Administer projects" seemed like a safe group to trust with exceptions to the rules).
• user drumm is in the "administrator" role, which has this perm... ;)

i'm not sure it's worth spending any time on code to change this, other than perhaps fixing the description field to more clearly spell out the rules (which is a little tricky, since the rules are site-specific and depend on admin settings). i could also re-visit if "Administer projects" really needs any exceptions to the rules anymore, since i think i've changed enough other things to make the validation only kick in when it should. for example, projects that aren't in CVS at all (e.g. the "webmaster" and "infrastructure" projects) can now be set so the "CVS repository" is [none], and then nothing is required on the "CVS directory" field).

anyway, sorry for the trouble. i at least fixed the CVS directory on your project, so now commits and tags should be associated with your project node, and the CVS ACL stuff will now work.

cheers,
-derek