Releases for Version Control / Project Node integration

Bug fix release, improving on the following issues:

• For files that don't belong to a given project, allow commit access (but keep denying branch and tag access). Seems I forgot to implement this distinction before.
• Update to the current Commit Log API, calling commitlog_commits_page() instead of commitlog_page().
• Add extra checks on query constraint emptyness in order to avoid badly formed SQL queries.

Production ready?

Finally, here's the real, feature complete "first stable release", coming to you in tandem with Version Control API 5.x-1.0-rc2. In comparison to the previous 1.3 release of the project node integration module, this one features the following last improvements (for now):

• Feature: Add a Developers page at "node//developers", and a list of user projects on the user page ("user/").
• Performance: Make an index out of (repo_id, directory), as it can't be unique but still benefits from being indexed.
• Bug fix, port of commit 85962 by dww (fixed issue #186932): Also allow version control admins to edit a project's commit access when they haven't got the 'administer nodes' permission.
• Nitpicking: No quotes around '%d' SQL placeholders anymore, life is better without them.

Project node integration (not counting release node integration) is now on par with the features in cvs.module, and improves on some of those. Now if we could get release node integration working similarly smooth, Drupal source code management would leave little to desire. Who wants to try?

Only one commit since the previous release, but the API addition is necessary for this patch to work, so this needs to be released now. One or two features are missing for the "final" 5.x release, but we're getting there.

• Remove the UNIQUE (repo_id, directory) as there can be multiple "empty" projects that have (0, '') for those values. Please give update.php a shot.
• Implement the "restrict project creation for users without VCS account" option (including the new API function versioncontrol_project_creation_is_allowed()). node_access() can't be hooked into, so for better usability we might want to get an additional patch into project.inc.
• Properly namespace the versioncontrol_get_projects_for_commit() function so that it's named versioncontrol_project_get_projects_for_commit().

Companion release for Version Control API 5.x-1.0-beta1, incorporating updates for one or two API changes in the main module.

Unfortunately, it seems I released 1.0 too early. I found that in addition to the cvs.module functionality, project.module also has two (smallish) features that I still need to implement in here. Also, the 1.0 release didn't clean up the variables properly, which is solved in this one. And finally, adapt to an API change of Version Control.

Use this release together with Version Control API 0.9-rc1.

At the moment, I consider this module both feature complete and bug free. Which seems like a good reason to release a 1.0 version.

New stuff since 1.0-rc1:

• Support for project type based project directory restrictions.
• Better apidox.
• That's it? Sounds like 1.0-rc1 was not far away from being released.

Now, on to finishing Version Control API itself, and then porting all of this to Drupal 6.

Initial release of the project node integration module. Or better, release candidate, as it should be tested a bit more thoroughly. Beat the crap out of this module, and enjoy your commit logs showing the associated projects for files inside a project directory.