Releases for Version Control / Project* integration

Release notes

Companion release to versioncontrol 6.x-1.0-rc1. Apart from minor bugfixes and improvements, this release comes with a wholly new module which fills in the last bit of functionality that was missing compared to cvs.module.

Say hello to the release node integration module, a.k.a. versioncontrol_release, which now ships with versioncontrol_project. When this module is enabled, release node creation and editing will be changed (for VCS backends that support this functionality) to a form where you can select tags and branches and create a release node associated to that tag or branch. Once a VCS-integrated release node is created, you can run the release script (versiocontrol_release/scripts/package-release-nodes.php - best run with cron, create appropriate configuration beforehand) and let that script generate tarballs for your site like drupal.org does for your releases.

The nice thing is that it will also work with VCS backends other than the CVS one, at least once support for that functionality has been implemented in the respective backend. Release node integration also degrades gracefully when the required functionality is not supported by a backend - in that case, standard release node creation will apply.

Other improvements compared to the last beta:

Release notes

Initial release of the project node integration module for Drupal 6. It is strongly advised to use this with the simultaneously released 6.x-1.0-beta4 release of Version Control API. There is no official 6.x release of Project* at the time of writing so you need to fetch the CVS HEAD version if you want to run this module. (Patches to regain independence from Project* are appreciated.)

In addition to the changes required for Drupal 6 compatibility, this release sports new database tables to keep track of associations of projects to repository items and version control operations. (Remember to run update.php in order to get those new tables created.) This moves a bit of processing work from the day-to-day queries to code that only needs to be executed when projects are modified or commits are recorded, and thus increases performance for common use cases. More improvements to appear in subsequent versioncontrol_project releases.

Release notes

Companion release to the great new Version Control API 5.x-2.0-alpha1. Features a link to the Commit Log in the project page, otherwise I can't remember anything user visible that you might notice, apart from the general superiority of the 5.x-2.x API of the module family.

Due to narrowing the scope of this module (ask hunmonk), the project node integration now only works for project nodes provided by the Project module. It's going to stay that way for the time being, although I hope to restore free selection of supported content types sometime in the future.

Release notes

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?

Release notes

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

Release notes

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.