Re: SCM systems?
- Posted by jeremy (admin) Aug 14, 2009
- 1058 views
I have not had problems with SVN either but I find that working with a distributed SCM is much easier, promotes branching when working on any long lasting change (more than a few hours) and allows me to commit more often, even when the resulting commit is no good. For instance, I may be working on removing DOS support and have done 1/3 of the standard library. I can safely commit because it's into my repo. Then I do another 1/3, and another 1/3. Finally, all the tests are passing and I push as one change back to the main repo.
Or, let's say I am working adding something new to the language. I can add it to the interpreter and my test.ex works, so I commit. I then run the unit tests and see that some fail, I fix the underlying problem and commit. I then move to the translator, commit. Run the demos, commit. Update the docs, commit. Push to the main repo.
It just makes more sense to me. I hope that we can move to a distributed SCM with OpenEuphoria. Oh, and these commits are instant since they are local. It's also easy to take a commit and push it to you or Matt to help me with a change I am stuck on or something. Oh... That brings up another point. I can commit to my local repo then sync on my OS X box with my local repo and make sure the changes still work on OS X, then again with Linux. Once they are working on the core OS's we support, I can push the resulting changes to the main repo.
Jeremy
