Hi,
I'm a bit conflicted about version control at the moment, and was hoping to get some input. I've used Subversion for quite some time, and love it for coding projects, it's the best thing since popcorn and I wouldn't do without it.
In the past I've also used it at work for 3D and animation project, which generally generates much larger amounts of data than code. We haven't used it for render output, but pretty much everything else. At one point we had a single repository that contained about 80gigs of data, though that was more of an exception rather than the rule.
While subversion is great in that it keeps things organized, as the extra mental step of adding and commiting files makes people more aware of what they're doing. When only saving to a shared file system, people have a tendency to put a lot of garbage files all over the place for some reason. For non-code files it has the following problems:
1. It's slow, checking out and commiting changes can take quite some time on big files.
2. It's used by non-coders. Artists tend to have trouble with using it and understanding it properly. Reverting to older versions is hard for them.
I'm more and more leaning towards just using a good incremental backup system and setup routines to keep the file structure clean. Though, I would love to hear your opinions.
I'm a bit conflicted about version control at the moment, and was hoping to get some input. I've used Subversion for quite some time, and love it for coding projects, it's the best thing since popcorn and I wouldn't do without it.
In the past I've also used it at work for 3D and animation project, which generally generates much larger amounts of data than code. We haven't used it for render output, but pretty much everything else. At one point we had a single repository that contained about 80gigs of data, though that was more of an exception rather than the rule.
While subversion is great in that it keeps things organized, as the extra mental step of adding and commiting files makes people more aware of what they're doing. When only saving to a shared file system, people have a tendency to put a lot of garbage files all over the place for some reason. For non-code files it has the following problems:
1. It's slow, checking out and commiting changes can take quite some time on big files.
2. It's used by non-coders. Artists tend to have trouble with using it and understanding it properly. Reverting to older versions is hard for them.
I'm more and more leaning towards just using a good incremental backup system and setup routines to keep the file structure clean. Though, I would love to hear your opinions.