versioncontrol_project 7.x-1.0-rc1

Git tag 7.x-1.0-rc1
New features
Bug fixes

Initial D7 release:

versioncontrol_project 7.x-1.x-dev

Git branch 7.x-1.x

Dev package for the main 7.x-1.x branch.

versioncontrol_project 6.x-2.0-beta1

Git tag 6.x-2.0-beta1
New features
Bug fixes

Changes since 6.x-1.0-rc2:

versioncontrol_project 6.x-2.x-dev

Git branch 6.x-2.x

Development snapshot for Version Control / Project Node integration.

versioncontrol_project 6.x-1.0-rc2

Git tag 6.x-1.0-rc2
New features

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.

versioncontrol_project 6.x-1.0-rc1

Git tag 6.x-1.0-rc1
New features
Bug fixes

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

Git tag 6.x-1.0-beta2
New features
Bug fixes

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.

versioncontrol_project 6.x-1.0-beta1

Git tag 6.x-1.0-beta1
New features

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.)

versioncontrol_project 5.x-2.0-rc1

Git tag 5.x-2.0-rc1

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.

versioncontrol_project 5.x-2.0-alpha1

Git tag 5.x-2.0-alpha1
New features
Bug fixes

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.

versioncontrol_project 5.x-1.5

Git tag 5.x-1.5
Bug fixes

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

Git tag 5.x-1.4
New features
Bug fixes

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):

versioncontrol_project 5.x-1.3

Git tag 5.x-1.3
New features
Bug fixes

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.

versioncontrol_project 5.x-1.2

Git tag 5.x-1.2
Bug fixes

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

Git tag 5.x-1.1
Bug fixes

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

Git tag 5.x-1.0
New features
Bug fixes

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

Git tag 5.x-1.0-rc1

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.

Subscribe with RSS Subscribe to Releases for Version Control / Project* integration