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.
Companion release to versioncontrol 6.x-1.0-beta4 in order to keep up with a small API change. No improvements or other changes in functionality compared to the beta1 release of the SVN backend.
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_svn 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.)
This release fixes two more bugs of the SVN backend, hopefully the last ones in the 5.x-2.x release cycle. So let's push out the "final" release, in parallel to Version Control API 5.x-2.0. Changes since versioncontrol_svn 5.x-2.0-rc2:
Second release candidate, with only a couple of code improvements that you probably won't notice as an end user. Still, as I'm forking off the Drupal 6 port now, the code has to be released in its latest form. Get this release if you're newly downloading the 5.x-2.x versions, or keep -rc1 if you are already a happy user.
Version Control API is going stable with 5.x-2.0-rc1, so the SVN backend has no reason to remain labeled as alpha. In fact, pretty much all features in here have been tested sufficiently well to make me claim bug-free operation, or at least no regressions whatsoever compared to the 5.x-1.x releases. Should reality prove me wrong (...nevaah!) then you can hunt us down in the issue queue.
Companion release to the great new Version Control API 5.x-2.0-alpha1. Apart from user-invisible porting work, good portions of direct repository access have also been implemented so that the SVN backend can be used with the Version Control API based repository viewer Repoview.