When you are working on a file, you often get this as result:
- Story.doc
- Story_Final.doc
- Story_Final_(now_really).doc
- Story_Final_(now_really_really).doc
- Story_Final_(now_really_really_this_one).doc
- Story_Final_(now_really)_last_changes.doc
- Story_Final_Def.doc
It starts with a single file but you end up with a lot of versions… (Or am I the only one?)
Years ago when I did my first project with a friend, we just gave each other a new version on floppy disc or cdrom. But the problem was that when we both worked on the same files we needed to merge the files. This was a real pain in the ass.
Last year I started to look for a automated solution for this problem, I found it! The solution to the common problem is Subversion.
In computing, Subversion (SVN) is a version control system initiated in 2000 by CollabNet Inc. It is used to maintain current and historical versions of files such as source code, web pages, and documentation.
I use this to manage most of my projects. The software just merges the different versions together!
So, if this sounds nice to you! Check it out.
Ps. The downside from all this geeky stuff is; you need a to have a Subversion Server. But luckily nowadays it’s real cheap to get one.
Great solution! Subversion is not only a revision controlled protocol but it also improves the workflow between projectmembers!
dreamhost.com is one of the few hosting companies that supports SVN. Unfortunately I wasn’t so lucky to have SVN on my hosting. My solution was to run a SVN server on my local computer that runs a apache based webserver… so i could use it outside my local network, the only thing is that your server must be online all the time.
For people who like to set up a SVN server on your local machine, don’t hesitate to contact me!
Subversion is great indeed and stops the hassle with 20/30 versions of one document.
Can you see it coming? Here it is: BUT…. One thing you shouldn’t forget is even when using subversion corrupt documents kicks you in the nuts. So always keep 2/3 copies of your document as backup.
Never had that problem! But i can imagine it..!
back to you!
can’t do without it, especially working with multiple programmers on one project!