This way all team members work in their own branch and regardless of when the change occurred they can commit their code back to the master. It is like creating a "merge" and "branch" every time you commit in SVN. There are DVCSes Distributed Version Control Systems! I can have a local repository and make all my commits to it, and then push/pull changes to a "master" repository. This is when I started wondering, "Why does Google use GIT repositories rather than SVN?" Well a quick search later. It has saved me more than a few times when a change or an important file is deleted. As a quick and dirty solution I am using Dropbox to keep version changes. It keeps happening more and more as I start working late or from home. Now I have lost SVN's rollback functionality while I'm away. what about when I have more than one bug fix? Every time I have a working version, and then a fix on the code there is a small chance that I will want to roll back. still not a problem, I can 'commit' the change the next day when I'm back. What happens when I make a quick bug fix at a client's office? Well. The work SVN is only accessible inside the company LAN.
What does a laptop have anything to do with it? Well, as long as I was at the office I had access to the repository, but when I'm at a client's place, that is another story.
It did everything that I was interested in. You can commit, branch, merge, keep changes or rollback mistakes. In my current company we use SVN, there are nice stand-alone programs on Windows & Linux that make integration easy and keep the command line well hidden. Or "that guy" that would "fix" your code when you weren't looking and break it even worse. It protected code from stupid fresh developers that would just delete files they weren't interested in. It was just about impossible to mess up the software. Then when I had my own team, I installed and used SVN. At my next company we used CVS, but I wasn't really collaborating with a team, so it was just a fancy backup. Well, it is also old-school and not free. VSS was at my first company, it was simple to use and just worked. I have some experience with Visual Source Safe, CVS and SVN. At the very base: it is a backup of your work, a snapshot in time for your development, and a sticky-note pasted development story. Even if you are the only developer, it is much more than a fancy backup system. A little heavy on memory, but that is unavoidable. Its free, and stable, and does almost everything in a standard way. I already prefer Eclipse as my IDE of choice. So we really should be talking about the development environment now.ġ) Free/Open source - Especially if I want to get some volunteers later on. It made me realize one thing: Version Control! I recently got a new development machine. For those that were waiting for a summary of JMonkey 3, Sorry.
0 kommentar(er)
