VerCon, a version control system

A version control system, or VCS in short, can save your life. By storing the different stages of your project’s development, it allows you to roll back in case of an error, collaborate with several other people on a single code base while avoiding accidental erasures...

I have used CVS, SVN, bazaar und Git. But for a simple personal project, I have always had the feeling that those tools were too complex with too many functionalities. For example, when I work alone on a code base, I do not need to create code branches, nor I need releases, or functionnality to ensure concurrent work. I also do not need functionnality to limit the list of folders and files to check in: I just want to commit everything, when I commit. I just need this:

• Commit everything
• Restore everything / some selected things from previous revisions.

So what will I do? Well of course, reinvent the wheel! It’s also a good way to redo some intensive coding and get into the specific issues of those tools: how does one efficiently store file differences in order to restore the older versions? How to handle different character encodings, binary files? How to create a fail-safe commit mechanism which ensures the repository will keep its consistency even in case of a crash of the project?

The solution: Vercon! For version control.

The project’s repository is private for now, but it will be made public as soon as this thing reaches Alpha 1.