Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Bug fix release. In short, this makes the xcvs-* trigger scripts work again (while adding a bit of helpful output for the committer). No changes otherwise, apart from fixing #366318: CVSModule_Compatibility missing component.
Companion release for versioncontrol 6.x-1.0-beta3, read its release notes for slightly more information. No 6.x-1.0-alpha1 versions are compatible with any 6.x-1.0-beta versions. Compatibility should be maintained from now on, though.
Companion testing release to Version Control API 6.x-1.0-alpha1. Should work just as flawlessly as versioncontrol_cvs 5.x-2.0, but like Version Control API itself, no guarantees about possible API or functionality changes until a stable 6.x-1.0 can be given. Therefore, this alpha1 might not work with future alphas, betas, release candidates or stable releases. (Or it might - who knows.)
The CVS backend seems solid as metal to me. No bug reports, no bugs I discovered by myself in a long time, it just works. Therefore, here's the 5.x-2.0 stable version, in parallel to Version Control API 5.x-2.0.
The single lonely fix in here since 5.x-2.0-rc2 is for the new cvs.module compatibility layer module, and does nothing more than making a menu path entry cached. And that's it.
The first stable release (candidate) that is compatible with the 5.x-2.x releases of Version Control API. The former 5.x-2.0-alpha1 of CVS backend had a pretty uncool bug (trying to write data to a table that is now gone, instead of sending it to Version Control API instead), so you'd better update to this one.
Companion release to the great new Version Control API 5.x-2.0-alpha1. Apart from user-invisible porting work and a more reliable mechanism to recognize re-additions of files as additions instead of modifications, the xcvs-* scripts have been improved in their branch/tag handling, which allows to control deleted tags using generic Version Control API facilities and fixes a couple of problems with tag moves.
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).
It works! Ship it!
...well it still doesn't contain CVS log parsing (I'm working on it, though) but it now comes with a README.txt for the xcvs-* hook scripts, and fixes a major bug in capturing commits. On the other hand, the option to combine multiple directory hook invocations into one commit (or tag/branch) message is now compulsory, thus the concerned option has been removed.
Companion release for Version Control API 5.x-1.0-rc3 (which is required for this release): fix Postgres support, make the uninstallation routine work properly, and don't attempt to handle repository and account forms of other backends.
Companion release for Version Control API 5.x-1.0-beta1, adapting to a few changes in the API module. Also, get_{branched,tagged}_items() works now instead of choking at an incorrect SQL query.
Postgres support, various bug fixes in the xcvs-* scripts, and a new (cron-driven) xcvs-generate-passwd.php script that can write the CVSROOT/passwd file from outside of Drupal.
Initial release, corresponding to the Version Control API release with the same release name. The only missing feature for 5.x-1.0 should be the "fetch history from log file" option, but apart from that there's no big changes pending. Fetch the tarball and have a great time!