Downloads
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:
- Make project page links work with current CVS versions of the Project module.
- When project issues are enabled, all project maintainers (users with commit access) are now able to assign issues to each other.
- Still work correctly with the current Version Control API release candidate, due to adapting to a small API change.
Can't be long, and previous users of the Subversion module will indeed get what they came for. We just need someone to implement a couple of functions in the SVN backend, then release tarballs for SVN projects are absolutely possible!
