Downloads

Download tar.gz 36.74 KB
MD5: 3d0d694cba9690063317f2bf9eea1e95
SHA-1: ec0186ea25087b8d7ddbd57d94b5f7e3852cfd85
SHA-256: 20d45ae1ab1097c0a4df78cb7705f86eff11da3166558a617660fcd1e0557beb
Download zip 47.53 KB
MD5: c4ee57419aaceebabfae27dfd75ff9d2
SHA-1: cdd67bafabf2b9f8aedfbb17dd174738964e6bf8
SHA-256: e8f236d6e0d346273430c3612265898c916106af498596f30f77a30c0202b003

Release notes

The companion release to Version Control API 5.x-1.0. At this point, the CVS backend supports everything that the original cvslog module did, with the obligatory exception (the "don't remove release tags" restriction - that's because there's no release node integration for Version Control API yet, and also because of issue #220175).

The major feature that justifies the 1.0 number is the CVS log parser that hasn't been ported until this release, and it now works like a charm. As an improvement to cvslog, both log parsing and trigger script modes now recognize re-added files even though CVS tells us they're just modified.

hunmonk also chipped in and provided multisite support for the trigger scripts, as well as the start of a cvslog -> versioncontrol_cvs porting script, but the latter does not yet cover commits and branches/tags. If you want to port your project*/cvslog setup to versioncontrol_cvs, you'll need to wait for the 6.x version.

In summary, the Version Control API plus Project Node Integration and the CVS backend still can't do everything that project* plus cvslog could - as the project release node integration is not there yet - but it already makes for a nice and reliable log viewer and commit access framework. Total feature parity is planned for the 6.x version of the three versioncontrol modules.

Created by: jpetso
Created on: 11 Feb 2008 at 02:25 UTC
Last updated: 11 Feb 2008 at 02:25 UTC
New features
Unsupported

Other releases