Hello

I need to be able to do project releases using subversion instead of CVS. I've looked at the subversion.module, but it's only for 4.7 and the site I'm building will use 5.0. I was wondering if anyone has a feeling for whether it would be better to start with the current subversion module and work to make it compatible with Drupal 5, or whether I should start with the HEAD version of the CVS module and work to make that compatible with subversion.

If I were to start with the CVS module, I'm guessing that converting it to a subversion module would require more than just searching/replacing CVS with subversion and changing the exec() statements to work with the subversion system instead of the CVS system. I'm not very familiar with CVS, so I'm not sure if it's structured differently enough that changing the module to work with subversion would be biting off more than I can chew.

Thanks for any suggestions
AC

Comments

dww’s picture

dww
we/he/they
commented
Status: Active » Closed (duplicate)

this is actually a huge undertaking that's been considered and discussed many times before.

short story: a bunch of the code in cvs.module needs to be made revision control system (RCS) independent and moved into a new project_rcs_api.module. cvs.module needs to shrink down to a tiny layer to implement the CVS-backend of the project RCS API, and subversion.module needs to also implement the SVN-backend of this API...

relevent issues to read:
http://drupal.org/node/69556
http://drupal.org/node/70125

related, but not directly about this:
http://drupal.org/node/19243
http://drupal.org/node/59694

also, some posts on in the http://groups.drupal.org/issue-tracking-and-software-releases group:
http://groups.drupal.org/node/790 (early discussion, i've changed my thoughts after the new release system).
http://groups.drupal.org/node/1047

if you're serious about this, let me know. it'd be a major effort, but quite a few people are interested in this. i'd be more than happy to help you figure out the code and start generating patches (we can do all of this in pieces) if you're up to the task. the very first step is to hash out exactly what the project_rcs API would look like, which a groups.drupal.org post would probably be the best place to do... we should just start a new one, given my current thoughts on how to make this work.

thanks,
-derek