Releases for Version Control / Project Node integration
versioncontrol_project 6.x-1.0-rc2
| Download | Size | md5 hash |
|---|---|---|
| versioncontrol_project-6.x-1.0-rc2.tar.gz | 47.52 KB | 0caf523c1ec072eb83015bc304a458c8 |
Catch-up release, implementing cvs.module's new "Maintainers" block (as seen on drupal.org's project pages) on Version Control API's new statistics API from the 6.x-1.0-rc2 release. And because that might not be sufficient in distributed-VCS scenarios, I also included the same block in a variant that not only includes project maintainers but all developers.
This release also updates the module's block deltas from integers to strings, so not only Version Control API itself but also this very module needs to be run through update.php.
Apart from that, no further changes compared to versioncontrol_project 6.x-1.0-rc1.
versioncontrol_project 6.x-1.0-rc1
| Download | Size | md5 hash |
|---|---|---|
| versioncontrol_project-6.x-1.0-rc1.tar.gz | 45.39 KB | afea880b43b92df45d78f8227fed54f7 |
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:
versioncontrol_project 6.x-1.0-beta2
| Download | Size | md5 hash |
|---|---|---|
| versioncontrol_project-6.x-1.0-beta2.tar.gz | 26.98 KB | f1bd9e3f040a846db177b59ddf5114fe |
Important update - ideally, you haven't yet triggered the code for slightly incorrect association of projects to items and operations. These issues should be fixed in this release, so it is highly recommended to update from beta1 as soon as possible.
Also note that this release depends on the API changes introduced with Version Control API 6.x-1.0-beta5, so any previous beta of Version Control API won't work correctly with this release of the project node integration module.
In return for the upgrading hassle, versioncontrol_project now provides "native" SQL query support for the 'nids' constraint, which makes for better performance (hopefully) and more flexibility by using the project/operation associations from the database.
versioncontrol_project 6.x-1.0-beta1
| Download | Size | md5 hash |
|---|---|---|
| versioncontrol_project-6.x-1.0-beta1.tar.gz | 26.79 KB | e2fd02023ea249bbd7eb2a72f2465fb2 |
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.
versioncontrol_project 5.x-2.0-rc1
| Download | Size | md5 hash |
|---|---|---|
| versioncontrol_project-5.x-2.0-rc1.tar.gz | 24.65 KB | 0d2e292e9b3250ebe193020ae72cc623 |
Relabeling the 5.x-2.0-alpha1 release of the Project Node Integration as 5.x-2.0-rc1, because it works just fine for me and Version Control API itself has also released its first 2.0 release candidate (so a stable release is in order). Read the linked alpha1 announcement for a tiny amount of nonetheless important info.
This release is recommended for everyone except for those who used it to integrate Drupal with project nodes not provided by the Project module. versioncontrol_project 5.x-2.x only works together with Project itself, which is not one of my favorite developments round here, but necessary for the time being. If you're using this module with Case Tracker, Organic Groups or whatever project node solution you might have, please do absolutely open an issue in the issue queue. I want to hear about who uses this module and how, and given sufficient interest I'd also like to bring back independence from the Project module.
Of course, the issue queue is also open for any other kind of request regarding Version Control / Project node integration.
versioncontrol_project 5.x-2.0-alpha1
| Download | Size | md5 hash |
|---|---|---|
| versioncontrol_project-5.x-2.0-alpha1.tar.gz | 24.65 KB | 90489fabaf0f072128016b8a565b3ea1 |
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.
versioncontrol_project 5.x-1.5
| Download | Size | md5 hash |
|---|---|---|
| versioncontrol_project-5.x-1.5.tar.gz | 20.17 KB | 1ac6649f5c13ed3b99530cdf6efb5ea3 |
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?
versioncontrol_project 5.x-1.4
| Download | Size | md5 hash |
|---|---|---|
| versioncontrol_project-5.x-1.4.tar.gz | 20.23 KB | a872a4d95534d5b3169b97d1bdaccdc6 |
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?
versioncontrol_project 5.x-1.3
| Download | Size | md5 hash |
|---|---|---|
| versioncontrol_project-5.x-1.3.tar.gz | 19.22 KB | a2770e00271e060743681003ce0c962b |
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 namedversioncontrol_project_get_projects_for_commit().
versioncontrol_project 5.x-1.2
| Download | Size | md5 hash |
|---|---|---|
| versioncontrol_project-5.x-1.2.tar.gz | 18.68 KB | 5d0127d6d356593c7a24b967c7f0716b |
Companion release for Version Control API 5.x-1.0-beta1, incorporating updates for one or two API changes in the main module.
versioncontrol_project 5.x-1.1
| Download | Size | md5 hash |
|---|---|---|
| versioncontrol_project-5.x-1.1.tar.gz | 18.65 KB | 506238d4c27590ef6da1db082505ad15 |
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.
versioncontrol_project 5.x-1.0
| Download | Size | md5 hash |
|---|---|---|
| versioncontrol_project-5.x-1.0.tar.gz | 18.5 KB | 3db9881fec90038b1e14cb9c0837d7da |
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.
versioncontrol_project 5.x-1.0-rc1
| Download | Size | md5 hash |
|---|---|---|
| versioncontrol_project-5.x-1.0-rc1.tar.gz | 18.2 KB | ffc7de75c0b41f091350e2b54becb58a |
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.
