Revision Control and Backups
Posted: Wed Jun 04, 2008 8:22 am
I just wanted to ask if you guys use any revision control system and/or if you have some backup system for your source code when developing. I found a couple of years old thread about this on the OS Development forum. Back then people seemed to be using CVS, Subversion and Darcs. What I'm wondering about is if the situation has changed and if using version control is now more widespread.
At my school (I study software engineering...) no teacher teaches anything about revision control. So the situation is indeed very depressing.
IMHO even if you work by yourself you can still use a RCS (Revision Control System). Indeed you probably should... if you use it properly you'll always have the history of your files available and can revert to a previous version if things go wrong. You can also develop different features in their own branches and merge them together gradually when they are mature enough. Not to mention that you can more easily work with other people if you happen to get someone join in your project.
I myself use Mercurial... it has installation packages for both Windows and Linux, its pretty easy to learn to use (at least the basics) and the CGI scripts (work fine with Apache) which come with it and the "hg serve" command help me put the repositories online fast (I like to browse the repositories through a web interface). I have a separate machine which holds the "central" repositories and that machine backs them up (using a combination of cron and a custom bash script) on an external disk.
And those who have never used a RCS (Revision Control System)... have you ever considered using one?
PS. Sorry, this seems to have turned into a sermon...
At my school (I study software engineering...) no teacher teaches anything about revision control. So the situation is indeed very depressing.
IMHO even if you work by yourself you can still use a RCS (Revision Control System). Indeed you probably should... if you use it properly you'll always have the history of your files available and can revert to a previous version if things go wrong. You can also develop different features in their own branches and merge them together gradually when they are mature enough. Not to mention that you can more easily work with other people if you happen to get someone join in your project.
I myself use Mercurial... it has installation packages for both Windows and Linux, its pretty easy to learn to use (at least the basics) and the CGI scripts (work fine with Apache) which come with it and the "hg serve" command help me put the repositories online fast (I like to browse the repositories through a web interface). I have a separate machine which holds the "central" repositories and that machine backs them up (using a combination of cron and a custom bash script) on an external disk.
And those who have never used a RCS (Revision Control System)... have you ever considered using one?
PS. Sorry, this seems to have turned into a sermon...