Ever heard of svk? http://svk.elixus.org, svk, it uses svn backend, but it enables interoperating with other versioning systems like cvs or perforce or even subversion

svk is an excelent showcase of perl prowess and it's ability to work with different existing repositories makes it easy to recommend to someone ( especially perl programmers ), because you're giving them just a great tool, not forcing them to 'upgrade'.

"Oh, you're using cvs? you shouldn't, move to svn" - yeah, right, and who's going to move existing repositories and THEN tell all other programmers that they should abandon cvs AND tools that use it ( like jDeveloper, go tell them that they should really be using vim and svn ).

With svk you can just use it yourself and it will push your patches/changesets to whatever your team is using (well, almost whatever, it will work with preforce, but won't work with highly proprietiary tools like bitkeeper)

svk looks promising, but personally, I don't think the documentation is there, yet. Whereas with subversion, there's the fantastic Subversion Book. Download, print, read and go. Perhaps somewhere down the line I'll feel that svk is worth a second look. The OP was looking for guidelines on future projects -- from a fresh start, I'd second taking a good hard look at subversion.

Regarding the migration challenge, the Subversion book includes an appendix on Subversion for CVS Users, which also discusses the latest tools for migrating a CVS directory to subversion.

-xdg

Code posted by xdg on PerlMonks is public domain. It has no warranties, express or implied. Posted code may not have been tested. Use at your own risk.