Getting ready to adopt Subversion

We have quite a lot of different projects and products. For historical
reasons, some of them live in a Linux-hosted CVS, and some are in
Microsoft VSS. They vary considerably in size, up to about 6,000,000
lines of source, but our use of them is pretty simple: we don't engage
in large-scale merging of branches, for example.

At the present, we want to move the VSS projects to SVN, because VSS
is going unsupported, and we don't fancy Team/System. We don't want
to change the CVS ones at the present time; that's a possibility for
later, but we are not having trouble with CVS and we've built a lot
of scripts on top of CVS that do useful things.

We have never /used/ SVN; a different development group recommended it.

The Linux server is SLES10sp2, which comes with SVN 1.3. Is it still
sane to use this old-ish version? I appreciate it may not be optimal,
but we are not very demanding, and it's easier than building a new
version.

I'd like to double-check that having CVS and SVN on the same server,
dealing with entirely separate repositories, is OK, and that there
aren't any ways for them to clash.

I'd also like to check on just how platform-independent a SVN
repository is. Can one just move the directory tree from Linux and run
it with a Windows SVN, or is there more to it than that? We understand
the line-endings issues thoroughly.

-- 
John Dallman
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2359480
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].